You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Gynn Rickerby (JIRA)" <ji...@codehaus.org> on 2011/01/21 04:26:58 UTC
[jira] Created: (MNG-4989) Properties defined in settings.xml not
being passed to dependent project dependency classifiers
Properties defined in settings.xml not being passed to dependent project dependency classifiers
-----------------------------------------------------------------------------------------------
Key: MNG-4989
URL: http://jira.codehaus.org/browse/MNG-4989
Project: Maven 2 & 3
Issue Type: Bug
Components: Dependencies, Inheritance and Interpolation, Profiles
Affects Versions: 3.0
Environment: Apache Maven 3.0 (r1004208; 2010-10-05 00:50:56+1300)
Java version: 1.6.0_22
Java home: C:\Program Files\Java\jdk1.6.0_22\jre
Default locale: en_NZ, platform encoding: Cp1252
OS name: "windows 7" version: "6.1" arch: "amd64" Family: "windows"
Reporter: Gynn Rickerby
Given the following projects and dependencies:
Project A -> Project B -> Project C
If Project B defines:
<dependency>
<groupId>ProjectC</groupId>
<artifact>ProjectC</artifact>
<version>1.0</version>
<classifier>${target.classifier}</classifier>
</dependency>
And the settings.xml contains:
<profile>
...
<properties>
<target.classifier>someclassifier</target.classifier>
</properties>
...
</profile>
Where the profile in question is the active profile.
Project B will build fine.
Project A will fail, with:
Failure to find ProjectC:ProjectC:${target.classifier}:1.0
--
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
[jira] Closed: (MNG-4989) Properties defined in settings.xml not
being passed to dependent project dependency classifiers
Posted by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-4989?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benjamin Bentmann closed MNG-4989.
----------------------------------
Resolution: Duplicate
Assignee: Benjamin Bentmann
> Properties defined in settings.xml not being passed to dependent project dependency classifiers
> -----------------------------------------------------------------------------------------------
>
> Key: MNG-4989
> URL: http://jira.codehaus.org/browse/MNG-4989
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Dependencies, Inheritance and Interpolation, Profiles
> Affects Versions: 3.0
> Environment: Apache Maven 3.0 (r1004208; 2010-10-05 00:50:56+1300)
> Java version: 1.6.0_22
> Java home: C:\Program Files\Java\jdk1.6.0_22\jre
> Default locale: en_NZ, platform encoding: Cp1252
> OS name: "windows 7" version: "6.1" arch: "amd64" Family: "windows"
> Reporter: Gynn Rickerby
> Assignee: Benjamin Bentmann
>
> Given the following projects and dependencies:
> Project A -> Project B -> Project C
> If Project B defines:
> <dependency>
> <groupId>ProjectC</groupId>
> <artifact>ProjectC</artifact>
> <version>1.0</version>
> <classifier>${target.classifier}</classifier>
> </dependency>
> And the settings.xml contains:
> <profile>
> ...
> <properties>
> <target.classifier>someclassifier</target.classifier>
> </properties>
> ...
> </profile>
> Where the profile in question is the active profile.
> Project B will build fine.
> Project A will fail, with:
> Failure to find ProjectC:ProjectC:${target.classifier}:1.0
--
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