[
http://jira.codehaus.org/browse/MNG-3057?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Henrik Brautaset Aronsen updated MNG-3057:
------------------------------------------
Attachment: maven-dependency-problem.zip
This issue is still not fixed in 2.1.0.
Steps to reproduce:
- download and unzip [^maven-dependency-problem.zip]
- cd first
- mvn clean install
- cd fourth
- mvn clean install (which fails)
The project layout is this:
{noformat}
first--+--second----third
|
+--fourth
{noformat}
"third" has "second" as parent version, and "second"/"fourth" has "first" as
parent version. They all use a common applicationVersion property, which is
set in "first". "fourth" has a dependency on "third", which resolves OK, but
it fails to resolve the transitive dependency to "second":
{code}
[INFO] Failed to resolve artifact.
GroupId: me
ArtifactId: second
Version: ${applicationVersion}
Reason: Unable to download the artifact from any repository
me:second:pom:${applicationVersion}
{code}
> properties not expanded in generated POMs when building A/B/C nested projects
> -----------------------------------------------------------------------------
>
> Key: MNG-3057
> URL: http://jira.codehaus.org/browse/MNG-3057
> Project: Maven 2
> Issue Type: Bug
> Components: Inheritance and Interpolation
> Affects Versions: 2.0.7
> Reporter: George Armhold
> Assignee: John Casey
> Fix For: 2.1.0
>
> Attachments: example.tar.gz, generated-poms.tar.gz,
> InstallMojo.java.patch, InstallMojo.java.patch,
> InstallMojo.quoteReplacement.patch, maven-dependency-problem.zip,
> maven-install-parent.patch
>
> Original Estimate: 0 minutes
> Remaining Estimate: 0 minutes
>
> Using Maven version: 2.0.8-SNAPSHOT, svn r547427.
> I checked out and built 2.0.8 because I was interested in Jason van Zyl's
> patch for MNG-2619- "building from the middle pom of a
> (parent,child,grandchild) heirarchy fails". The fix works for the most part,
> but there still seems to be a problem with the poms that get generated during
> the install goal. The poms that get installed into .m2/repository do not
> have properties interpolated. If I run maven like:
> $ mvn install -Dglobal-version=1.0.0
> I get poms with the string "${global-version}" embedded in the resulting poms
> rather than what I specify on the command line (or in settings.xml). The
> build works properly aside from this, and if I do "mvn help:effective-pom"
> the properties are correctly interpolated.
> I've attached a tarfile with an example A/B/C build structure that exhibits
> this behavior, as well as the generated poms.
> Many thanks for your attention.
--
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
