You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Christian Moser (JIRA)" <ji...@codehaus.org> on 2010/01/19 12:40:55 UTC
[jira] Created: (MNG-4538) dependencyManagament dependencies within
profiles are not activated by settings.xml
dependencyManagament dependencies within profiles are not activated by settings.xml
------------------------------------------------------------------------------------
Key: MNG-4538
URL: http://jira.codehaus.org/browse/MNG-4538
Project: Maven 2 & 3
Issue Type: Bug
Affects Versions: 2.2.1, 3.0-alpha-7
Environment: Windows XP
Reporter: Christian Moser
Priority: Critical
Attachments: profileBug.zip
This issue is *not* reproducable with Maven 2.0.9, 2.0.10 and 2.2.2-RC1-SNAPSHOT.
I'm referring to the sample projects contained in profileBug.zip:
preparation:
- You need to set in your settings.xml:
<activeProfiles>
<activeProfile>testing</activeProfile>
</activeProfiles>
- Install main-parent
reproducing:
- Install project parent. This will fail because of ChildTwo.
The transivite dependency of junit is not beeing resolved correctly through project ChildOne even it's not necessary. I guess not finding commons-lang is just a "sequence error" of the "invalid" pom of ChildOne.
It seems like the profile isn't activated by the settings.xml and so the dependencies aren't known in context of project ChildTwo transitive dependencies.
But e.g. childOne or childThree can be installed without any problems so the profile should be loaded correctly, the only difference to ChildTwo is that they don't have any transitive dependencies to other projects with the same parent.
If you cange in project parent the profile "testing" to:
<activation>
<activeByDefault>true</activeByDefault>
</activation>
or change the profile activation by property and install project parent with -Dtesting, childTwo will be installed correctly.
This issue only occurs with maven 3.0 or 2.2.1. It works fine with maven 2.0.10 or 2.2.2-RC1-SNAPSHOT
Will this error be fixed in maven 3.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] Issue Comment Edited: (MNG-4538) dependencyManagament
dependencies within profiles are not activated by settings.xml
Posted by "Christian Moser (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-4538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=207454#action_207454 ]
Christian Moser edited comment on MNG-4538 at 1/19/10 6:42 AM:
---------------------------------------------------------------
read the last two comments in MNG-1388, please
was (Author: onmomo):
read the last two comments, please
> dependencyManagament dependencies within profiles are not activated by settings.xml
> ------------------------------------------------------------------------------------
>
> Key: MNG-4538
> URL: http://jira.codehaus.org/browse/MNG-4538
> Project: Maven 2 & 3
> Issue Type: Bug
> Affects Versions: 2.2.1, 3.0-alpha-7
> Environment: Windows XP
> Reporter: Christian Moser
> Priority: Critical
> Attachments: profileBug.zip
>
>
> This issue is *not* reproducable with Maven 2.0.9, 2.0.10 and 2.2.2-RC1-SNAPSHOT.
> I'm referring to the sample projects contained in profileBug.zip:
> preparation:
> - You need to set in your settings.xml:
> <activeProfiles>
> <activeProfile>testing</activeProfile>
> </activeProfiles>
> - Install main-parent
> reproducing:
> - Install project parent. This will fail because of ChildTwo.
> The transivite dependency of junit is not beeing resolved correctly through project ChildOne even it's not necessary. I guess not finding commons-lang is just a "sequence error" of the "invalid" pom of ChildOne.
> It seems like the profile isn't activated by the settings.xml and so the dependencies aren't known in context of project ChildTwo transitive dependencies.
> But e.g. childOne or childThree can be installed without any problems so the profile should be loaded correctly, the only difference to ChildTwo is that they don't have any transitive dependencies to other projects with the same parent.
> If you cange in project parent the profile "testing" to:
> <activation>
> <activeByDefault>true</activeByDefault>
> </activation>
> or change the profile activation by property and install project parent with -Dtesting, childTwo will be installed correctly.
> This issue only occurs with maven 3.0 or 2.2.1. It works fine with maven 2.0.10 or 2.2.2-RC1-SNAPSHOT
> Will this error be fixed in maven 3.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-4538) dependencyManagament dependencies within
profiles are not activated by settings.xml
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-4538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter closed MNG-4538.
-----------------------------
Resolution: Duplicate
Assignee: Brett Porter
note that this is likely to be rolled back, so you can expect the behaviour in 2.2.1 and 3.0-SNAPSHOT to be permanent. Applying profiles to POMs built from the repository can lead to inconsistent build behaviour across machines - I think the fact this reproduction example was so confusing to find the cause illustrates that.
> dependencyManagament dependencies within profiles are not activated by settings.xml
> ------------------------------------------------------------------------------------
>
> Key: MNG-4538
> URL: http://jira.codehaus.org/browse/MNG-4538
> Project: Maven 2 & 3
> Issue Type: Bug
> Affects Versions: 2.2.1, 3.0-alpha-7
> Environment: Windows XP
> Reporter: Christian Moser
> Assignee: Brett Porter
> Priority: Critical
> Attachments: profileBug.zip
>
>
> This issue is *not* reproducable with Maven 2.0.9, 2.0.10 and 2.2.2-RC1-SNAPSHOT.
> I'm referring to the sample projects contained in profileBug.zip:
> preparation:
> - You need to set in your settings.xml:
> <activeProfiles>
> <activeProfile>testing</activeProfile>
> </activeProfiles>
> - Install main-parent
> reproducing:
> - Install project parent. This will fail because of ChildTwo.
> The transivite dependency of junit is not beeing resolved correctly through project ChildOne even it's not necessary. I guess not finding commons-lang is just a "sequence error" of the "invalid" pom of ChildOne.
> It seems like the profile isn't activated by the settings.xml and so the dependencies aren't known in context of project ChildTwo transitive dependencies.
> But e.g. childOne or childThree can be installed without any problems so the profile should be loaded correctly, the only difference to ChildTwo is that they don't have any transitive dependencies to other projects with the same parent.
> If you cange in project parent the profile "testing" to:
> <activation>
> <activeByDefault>true</activeByDefault>
> </activation>
> or change the profile activation by property and install project parent with -Dtesting, childTwo will be installed correctly.
> This issue only occurs with maven 3.0 or 2.2.1. It works fine with maven 2.0.10 or 2.2.2-RC1-SNAPSHOT
> Will this error be fixed in maven 3.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] Commented: (MNG-4538) dependencyManagament dependencies
within profiles are not activated by settings.xml
Posted by "Christian Moser (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-4538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=207460#action_207460 ]
Christian Moser commented on MNG-4538:
--------------------------------------
I've found a different behavior of maven 2.2.1 & 3.0
maven 2.2.1: You're able to install project parent recursive, but installing project childTwo will fail.
maven 3.0: You aren't able to install project parent recursive, neither you can install childTwo.
> dependencyManagament dependencies within profiles are not activated by settings.xml
> ------------------------------------------------------------------------------------
>
> Key: MNG-4538
> URL: http://jira.codehaus.org/browse/MNG-4538
> Project: Maven 2 & 3
> Issue Type: Bug
> Affects Versions: 2.2.1, 3.0-alpha-7
> Environment: Windows XP
> Reporter: Christian Moser
> Priority: Critical
> Attachments: profileBug.zip
>
>
> This issue is *not* reproducable with Maven 2.0.9, 2.0.10 and 2.2.2-RC1-SNAPSHOT.
> I'm referring to the sample projects contained in profileBug.zip:
> preparation:
> - You need to set in your settings.xml:
> <activeProfiles>
> <activeProfile>testing</activeProfile>
> </activeProfiles>
> - Install main-parent
> reproducing:
> - Install project parent. This will fail because of ChildTwo.
> The transivite dependency of junit is not beeing resolved correctly through project ChildOne even it's not necessary. I guess not finding commons-lang is just a "sequence error" of the "invalid" pom of ChildOne.
> It seems like the profile isn't activated by the settings.xml and so the dependencies aren't known in context of project ChildTwo transitive dependencies.
> But e.g. childOne or childThree can be installed without any problems so the profile should be loaded correctly, the only difference to ChildTwo is that they don't have any transitive dependencies to other projects with the same parent.
> If you cange in project parent the profile "testing" to:
> <activation>
> <activeByDefault>true</activeByDefault>
> </activation>
> or change the profile activation by property and install project parent with -Dtesting, childTwo will be installed correctly.
> This issue only occurs with maven 3.0 or 2.2.1. It works fine with maven 2.0.10 or 2.2.2-RC1-SNAPSHOT
> Will this error be fixed in maven 3.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