You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Chad Moats (JIRA)" <ji...@codehaus.org> on 2006/12/19 20:32:40 UTC
[jira] Created: (MECLIPSE-208) Implicit dependencies are not
resolved when using make-artifacts with stripQualifier=false
Implicit dependencies are not resolved when using make-artifacts with stripQualifier=false
------------------------------------------------------------------------------------------
Key: MECLIPSE-208
URL: http://jira.codehaus.org/browse/MECLIPSE-208
Project: Maven 2.x Eclipse Plugin
Issue Type: Bug
Components: PDE support
Affects Versions: 2.3
Environment: Windows XP, Eclipse 3.3 M4
Reporter: Chad Moats
When using qualifiers with the make-artifacts goal, implict dependencies cannot be resolved because they fall outside the version range used. This issue was found when trying to deploy Eclipse 3.3 M4 to my local repository while retaining the qualifier. For example, the org.eclipse.core.runtime pom that is gernerated states that it depends on org.eclipse.equinox.app using the range of [1.0.0,2.0.0). The actual version number of the org.eclipse.equinox.app is 1.0.0-vxxxx. Using a qualifier means that the version actually falls before the 1.0.0-2.0.0 range. The following error is logged:
Couldn't find a version in [1.0.0-v20061208] to match range [1.0.0,2.0.0)
org.eclipse.equinox:org.eclipse.equinox.app:jar:null
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MECLIPSE-208) Implicit dependencies are not
resolved when using make-artifacts with stripQualifier=false
Posted by "Matthew Beermann (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MECLIPSE-208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matthew Beermann updated MECLIPSE-208:
--------------------------------------
Attachment: MECLIPSE-208-maven-eclipse-plugin.patch
> Implicit dependencies are not resolved when using make-artifacts with stripQualifier=false
> ------------------------------------------------------------------------------------------
>
> Key: MECLIPSE-208
> URL: http://jira.codehaus.org/browse/MECLIPSE-208
> Project: Maven 2.x Eclipse Plugin
> Issue Type: Bug
> Components: PDE support
> Affects Versions: 2.3
> Environment: Windows XP, Eclipse 3.3 M4
> Reporter: Chad Moats
> Attachments: MECLIPSE-208-maven-eclipse-plugin.patch, MECLIPSE-208-maven-eclipse-plugin.patch
>
>
> When using qualifiers with the make-artifacts goal, implict dependencies cannot be resolved because they fall outside the version range used. This issue was found when trying to deploy Eclipse 3.3 M4 to my local repository while retaining the qualifier. For example, the org.eclipse.core.runtime pom that is gernerated states that it depends on org.eclipse.equinox.app using the range of [1.0.0,2.0.0). The actual version number of the org.eclipse.equinox.app is 1.0.0-vxxxx. Using a qualifier means that the version actually falls before the 1.0.0-2.0.0 range. The following error is logged:
> Couldn't find a version in [1.0.0-v20061208] to match range [1.0.0,2.0.0)
> org.eclipse.equinox:org.eclipse.equinox.app:jar:null
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Issue Comment Edited: (MECLIPSE-208) Implicit dependencies
are not resolved when using make-artifacts with stripQualifier=false
Posted by "Michael Vorburger (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MECLIPSE-208?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=131157#action_131157 ]
vorburger edited comment on MECLIPSE-208 at 4/17/08 1:15 PM:
---------------------------------------------------------------------
This is annoying... would be wonderful if this could get fixed somehow... see also http://fornax-platform.org/cp/display/fornax/2.+Hello+World+Tutorial+%28CSC%29?focusedCommentId=2098#comment-2098.
was (Author: vorburger):
This is annoying... would be wonderful if this could get fixed something... see also http://fornax-platform.org/cp/display/fornax/2.+Hello+World+Tutorial+%28CSC%29?focusedCommentId=2098#comment-2098.
> Implicit dependencies are not resolved when using make-artifacts with stripQualifier=false
> ------------------------------------------------------------------------------------------
>
> Key: MECLIPSE-208
> URL: http://jira.codehaus.org/browse/MECLIPSE-208
> Project: Maven 2.x Eclipse Plugin
> Issue Type: Bug
> Components: PDE support
> Affects Versions: 2.3
> Environment: Windows XP, Eclipse 3.3 M4
> Reporter: Chad Moats
> Attachments: MECLIPSE-208-maven-eclipse-plugin.patch
>
>
> When using qualifiers with the make-artifacts goal, implict dependencies cannot be resolved because they fall outside the version range used. This issue was found when trying to deploy Eclipse 3.3 M4 to my local repository while retaining the qualifier. For example, the org.eclipse.core.runtime pom that is gernerated states that it depends on org.eclipse.equinox.app using the range of [1.0.0,2.0.0). The actual version number of the org.eclipse.equinox.app is 1.0.0-vxxxx. Using a qualifier means that the version actually falls before the 1.0.0-2.0.0 range. The following error is logged:
> Couldn't find a version in [1.0.0-v20061208] to match range [1.0.0,2.0.0)
> org.eclipse.equinox:org.eclipse.equinox.app:jar:null
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MECLIPSE-208) Implicit dependencies are not
resolved when using make-artifacts with stripQualifier=false
Posted by "Michael Vorburger (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MECLIPSE-208?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=131157#action_131157 ]
Michael Vorburger commented on MECLIPSE-208:
--------------------------------------------
This is annoying... would be wonderful if this could get fixed something... see also http://fornax-platform.org/cp/display/fornax/2.+Hello+World+Tutorial+%28CSC%29?focusedCommentId=2098#comment-2098.
> Implicit dependencies are not resolved when using make-artifacts with stripQualifier=false
> ------------------------------------------------------------------------------------------
>
> Key: MECLIPSE-208
> URL: http://jira.codehaus.org/browse/MECLIPSE-208
> Project: Maven 2.x Eclipse Plugin
> Issue Type: Bug
> Components: PDE support
> Affects Versions: 2.3
> Environment: Windows XP, Eclipse 3.3 M4
> Reporter: Chad Moats
> Attachments: MECLIPSE-208-maven-eclipse-plugin.patch
>
>
> When using qualifiers with the make-artifacts goal, implict dependencies cannot be resolved because they fall outside the version range used. This issue was found when trying to deploy Eclipse 3.3 M4 to my local repository while retaining the qualifier. For example, the org.eclipse.core.runtime pom that is gernerated states that it depends on org.eclipse.equinox.app using the range of [1.0.0,2.0.0). The actual version number of the org.eclipse.equinox.app is 1.0.0-vxxxx. Using a qualifier means that the version actually falls before the 1.0.0-2.0.0 range. The following error is logged:
> Couldn't find a version in [1.0.0-v20061208] to match range [1.0.0,2.0.0)
> org.eclipse.equinox:org.eclipse.equinox.app:jar:null
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MECLIPSE-208) Implicit dependencies are not
resolved when using make-artifacts with stripQualifier=false
Posted by "Matthew Beermann (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MECLIPSE-208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matthew Beermann updated MECLIPSE-208:
--------------------------------------
Attachment: MECLIPSE-208-maven-eclipse-plugin.patch
I believe that this patch solves the issue.
> Implicit dependencies are not resolved when using make-artifacts with stripQualifier=false
> ------------------------------------------------------------------------------------------
>
> Key: MECLIPSE-208
> URL: http://jira.codehaus.org/browse/MECLIPSE-208
> Project: Maven 2.x Eclipse Plugin
> Issue Type: Bug
> Components: PDE support
> Affects Versions: 2.3
> Environment: Windows XP, Eclipse 3.3 M4
> Reporter: Chad Moats
> Attachments: MECLIPSE-208-maven-eclipse-plugin.patch
>
>
> When using qualifiers with the make-artifacts goal, implict dependencies cannot be resolved because they fall outside the version range used. This issue was found when trying to deploy Eclipse 3.3 M4 to my local repository while retaining the qualifier. For example, the org.eclipse.core.runtime pom that is gernerated states that it depends on org.eclipse.equinox.app using the range of [1.0.0,2.0.0). The actual version number of the org.eclipse.equinox.app is 1.0.0-vxxxx. Using a qualifier means that the version actually falls before the 1.0.0-2.0.0 range. The following error is logged:
> Couldn't find a version in [1.0.0-v20061208] to match range [1.0.0,2.0.0)
> org.eclipse.equinox:org.eclipse.equinox.app:jar:null
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MECLIPSE-208) Implicit dependencies are not
resolved when using make-artifacts with stripQualifier=false
Posted by "Jochen Wiedmann (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MECLIPSE-208?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=186784#action_186784 ]
Jochen Wiedmann commented on MECLIPSE-208:
------------------------------------------
Workaround: Use the -DstripQualifier=true parameter. Maps the version numbers from 3.5.0-vSomething to 3.5.0.
> Implicit dependencies are not resolved when using make-artifacts with stripQualifier=false
> ------------------------------------------------------------------------------------------
>
> Key: MECLIPSE-208
> URL: http://jira.codehaus.org/browse/MECLIPSE-208
> Project: Maven 2.x Eclipse Plugin
> Issue Type: Bug
> Components: PDE support
> Affects Versions: 2.3
> Environment: Windows XP, Eclipse 3.3 M4
> Reporter: Chad Moats
> Attachments: MECLIPSE-208-maven-eclipse-plugin.patch, MECLIPSE-208-maven-eclipse-plugin.patch
>
>
> When using qualifiers with the make-artifacts goal, implict dependencies cannot be resolved because they fall outside the version range used. This issue was found when trying to deploy Eclipse 3.3 M4 to my local repository while retaining the qualifier. For example, the org.eclipse.core.runtime pom that is gernerated states that it depends on org.eclipse.equinox.app using the range of [1.0.0,2.0.0). The actual version number of the org.eclipse.equinox.app is 1.0.0-vxxxx. Using a qualifier means that the version actually falls before the 1.0.0-2.0.0 range. The following error is logged:
> Couldn't find a version in [1.0.0-v20061208] to match range [1.0.0,2.0.0)
> org.eclipse.equinox:org.eclipse.equinox.app:jar:null
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira