maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benjamin Bentmann (JIRA)" <>
Subject [jira] Updated: (MNG-3782) Variable substition not performed in transitive dependency using value from active profile
Date Mon, 23 Nov 2009 09:41:55 GMT


Benjamin Bentmann updated MNG-3782:

    Fix Version/s:     (was: 3.0-alpha-5)

> Variable substition not performed in transitive dependency using value from active profile
> ------------------------------------------------------------------------------------------
>                 Key: MNG-3782
>                 URL:
>             Project: Maven 2
>          Issue Type: Bug
>          Components: Dependencies
>    Affects Versions: 3.0-alpha-1
>         Environment: Java version: 1.6.0_07
> OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows"
>            Reporter: Robert Varttinen
>             Fix For: 3.x
>         Attachments: build.log,,,,
> When invoking the 'mvn compile' command and a profile is active, defined in settings.xml,
a variable substitution is not performed in a transitive dependency. 
> In the example provided the project to be built, C, depends on B which in its turn depends
on A. The versions of B and A to be used are defined in a profile, the POM-files defines a
variable indicating the versions. The profile in question is defined in the settings.xml and
is always active (check with command 'mvn help:active-profiles'). The results of project A
and B are successfully built and installed in the local repository. 
> Invoking a build for project C using a command line parameter indicating, 'mvn compile
-Dparentversion=0.0.1-SNAPSHOT, the versions render a successful build. The transitive dependency
is resolved correctly. 
> This problem is also visible in Eclipse, m2eclipse, as the project C in the example provided,
does not build (error indication). The example provided includes Eclipse projects displaying
this (version of the Eclipse plugin is used). 
> The settings.xml and a build log are provided as attachments to this issue. 

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message