[
http://jira.codehaus.org/browse/MECLIPSE-675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=242821#action_242821
]
Steve Armstrong commented on MECLIPSE-675:
------------------------------------------
Sorry, here's the full link to the m2e bug:
https://issues.sonatype.org/browse/MNGECLIPSE-1649
> downloadSources will not attach artifact-5-sources.jar to artifact-5-jar.jar
> ----------------------------------------------------------------------------
>
> Key: MECLIPSE-675
> URL: http://jira.codehaus.org/browse/MECLIPSE-675
> Project: Maven 2.x Eclipse Plugin
> Issue Type: Bug
> Components: Core : Dependencies resolution and build path
> (.classpath)
> Affects Versions: 2.8
> Environment: Windows7_x64
> Reporter: Steve Armstrong
> Attachments: patch.txt
>
>
> When depending on a project that has WAR as the default artifact, my project
> uses
> <dependency>
> <groupId>group</groupId>
> <artifactId>artifact</artifactId>
> <version>5</version>
> <classifier>jar</classifier>
> </dependency>
> This results in no attached sources for that jar in Eclipse. m2eclipse has
> raised the same issue but in reverse: MNGECLIPSE-1649
> It seems when building the project above, artifact-5-jar-sources.jar is
> produced in the target folder, but when installed to the local repo (and
> deployed to the remote repo), it renames the file to artifact-5-sources.jar
> The diff attached changes the lookup behaviour to not include the classifier
> unless it's "tests". This will bring it in line with m2e's lookup.
--
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
