[
http://jira.codehaus.org/browse/MECLIPSE-287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Max Bowsher updated MECLIPSE-287:
---------------------------------
Attachment: test-project-33.patch
Patch introducing test which tests *both* MECLIPSE-287 and MECLIPSE-151.
NB: In addition to the patch, the MECLIPSE-151 part of the test requires that
someone create a zero-length file
"src/test/resources/m2repo/maven/maven-core/98.0/maven-core-98.0-test-sources.jar"
- this is not part of the patch, because the patch format does not seem to be
able to represent the creation of a zero-length file properly.
> Regression - fails to correctly construct classpath containing dependencies
> with classifiers
> --------------------------------------------------------------------------------------------
>
> Key: MECLIPSE-287
> URL: http://jira.codehaus.org/browse/MECLIPSE-287
> Project: Maven 2.x Eclipse Plugin
> Issue Type: Bug
> Affects Versions: 2.4
> Reporter: Max Bowsher
> Priority: Blocker
> Fix For: 2.4
>
> Attachments: test-project-33.patch
>
>
> I have a project that depends on foo-1.0.jar and foo-1.0-tests.jar - i.e.,
> the second is a dependency with a <classifier>tests</classifier>.
> With maven-eclipse-plugin 2.3, both jars are correctly added to the Eclipse
> .classpath.
> With maven-eclipse-plugin 2.4-SNAPSHOT, only one of the jars is placed on the
> classpath, resulting in compile failure due to missing classes. Examining the
> code, it appears that the dependency resolution in AbstractIdeSupportMojo,
> and the data class IdeDependency, completely ignore the concept of
> classifier. Thus, the classifier information is discarded in the conversion
> from Artifact to IdeDependency,
--
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
