[
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
