[
http://jira.codehaus.org/browse/MNG-2957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brett Porter updated MNG-2957:
------------------------------
Fix Version/s: (was: Reviewed Pending Version Assignment)
2.0.x
Component/s: Inheritance and Interpolation
> attached artifact is not included in classpath when a sub-project depended on
> it is compiled in multi-project
> -------------------------------------------------------------------------------------------------------------
>
> Key: MNG-2957
> URL: http://jira.codehaus.org/browse/MNG-2957
> Project: Maven 2
> Issue Type: Bug
> Components: Inheritance and Interpolation
> Affects Versions: 2.0.6
> Reporter: YOKOTA Takehiko
> Fix For: 2.0.x
>
>
> I have a mult-project. It contains two sub-project A and B, and A has an
> attached artifact A.jar (main artifact is A.zip).
> In addition, B depends on A.jar in compile scope. When I build this
> mult-project like 'mvn install', it fails because
> A.jar is not included in the classpath for compiling B.
> The reason is that, as for A.jar,
> org.apache.maven.project.MavenProject#replaceWithActiveArtifact() returns a
> copied Artifact
> of the AttachedArtifact object created by
> org.apache.maven.projectMavenProjectHelper#attachArtifact() and
> the value of its scope property is null. So this Artifact is ignored in
> MavenProject#getCompileClasspathElements().
> In MavenProject#replaceWithActiveArtifact(), the scope property's value of a
> copied Artifact from attached should be the
> same as one's value of pluginArtifact.
--
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
