[
http://jira.codehaus.org/browse/MECLIPSE-287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_100797
]
Max Bowsher commented on MECLIPSE-287:
--------------------------------------
Some further explanation about why I had to write a test that combines two
issues:
In producing an appropriate expected/.classpath file, I found that the form of
a classpathentry required to test MECLIPSE-287 depends on whether MECLIPSE-151
is fixed. It did not seem appropriate to write a test which required the
*brokenness* of MECLIPSE-151 in order to pass, so I settled for writing a test
that requires both issues to be fixed, to pass.
> 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
