maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From wolfgang häfelinger (JIRA) <j...@codehaus.org>
Subject [jira] Reopened: (MPH-84) Inherited profile activation not working within local POM
Date Thu, 24 Mar 2011 08:46:22 GMT

     [ http://jira.codehaus.org/browse/MPH-84?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

wolfgang häfelinger reopened MPH-84:
------------------------------------


I disagree. 

Issue MPH-79 is about plugin help listing profiles incorrectly. The issue is, as clearly written,
not about that help plugin but rather that profile activation works using external properties
(command line, settings) but NOT by setting properties within the local POM.

> Inherited profile activation not working within local POM
> ---------------------------------------------------------
>
>                 Key: MPH-84
>                 URL: http://jira.codehaus.org/browse/MPH-84
>             Project: Maven 2.x Help Plugin
>          Issue Type: Bug
>    Affects Versions: 2.1.1
>         Environment: Tested with M3.0.2 and M2.2.1 on MacOS X (OS surely not relevant)
>            Reporter: wolfgang häfelinger
>            Assignee: Benjamin Bentmann
>         Attachments: MNG-3228.zip
>
>
> This demo consists of four file:
> (1) README.txt
> (2) pom.xml
> (3) parent-pom.xml
> (4) pom-no-profile-no-dep.xml
> File" pom.xml" is the POM expected to activate profile "logging" defined in "parent-pom.xml".
This does not work as clearly outlined in the original bug report MNG-3228 [http://jira.codehaus.org/browse/MNG-3228].
> File "pom-no-profile-no-dep.xml" is essentially the same as file "pom.xml". Section <dependencies
/> and profile activation has been removed in order to get goal "help:effective-profiles"
working.
> The demo works like this: Install parent POM in local cache (~/.m2/repository).
> % mvn -f parent-pom.xml install
> Then try this:
> Test 1:
> % mvn -f pom.xml package
> => error
> Test 2:
> % mvn -f pom.xml package -Dactivate-profile-logging=true
> => good
> Test 3:
> % mvn -f pom.xml package -Plogging=true
> => good
> Test 4:
> % mvn -f pom-no-profile-no-dep.xml help:active-profiles
> => profile "logging" is not shown (expeced, but see next test)
> Test 5:
> % mvn -f pom-no-profile-no-dep.xml help:active-profiles -Dactivate-profile-logging=true
> => does not show profile "logging" although "logging" must be active (otherwise: why
would second test work?)
> Summary:
> 1. maven-help-plugin can't be trusted on reporting active profiles.
> 2. Activating inherited profiles differs from activating local profiles. 
> The second issue is clearly (!) a design bug cause there is no good reason why inherited
elements behave differently from local elements.

-- 
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

       

Mime
View raw message