[
http://jira.codehaus.org/browse/MNG-3420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=130895#action_130895
]
Dimitar Raynov commented on MNG-3420:
-------------------------------------
I have this error too so i hope it will be resolved in the next version !
> In a reactor, attached artifacts with classifier should be used when
> generating classpath, instead of the whole output directory of the related
> project
> -------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: MNG-3420
> URL: http://jira.codehaus.org/browse/MNG-3420
> Project: Maven 2
> Issue Type: Bug
> Components: Reactor and workspace
> Affects Versions: 2.0.5, 2.0.6, 2.0.7, 2.0.8
> Reporter: Nicolas Rougé
> Attachments: MavenProject-patch.txt, test-classifier.tar.gz
>
>
> In a reactor, when a project depends on attached artifacts with classifier of
> other projects (such as jar assemblies), the generated classpath includes all
> the output directory of the related projects.
> This can lead to problems for example if these attached artifacts contains
> only a subset of the output directory of the related project.
> I attached an example that shows this problem :
> 1/ launch "mvn install" in the "test-classifier" directory (POM project
> basedir), you'll get a compilation failure for module3.
> 2/ launch "mvn install" in the "module3" directory, it works.
> I also attached a patch (it affects only MavenProject class).
--
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
