[
http://jira.codehaus.org/browse/MNG-3897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brett Porter updated MNG-3897:
------------------------------
Fix Version/s: 2.0.x
> Profile with jdk activation is not inherited from parent pom
> ------------------------------------------------------------
>
> Key: MNG-3897
> URL: http://jira.codehaus.org/browse/MNG-3897
> Project: Maven 2
> Issue Type: Bug
> Components: Profiles
> Affects Versions: 2.0.9
> Environment: Windows, JDK 1.6.0_07
> Reporter: Anthony Whitford
> Fix For: 2.0.x
>
> Attachments: mvn-bug.zip
>
>
> If I declare a profile in a parent pom with jdk activation, it isn't being
> activated for projects that inherit the parent pom.
> (Note that I think profiles in general are being inherited. I suspect this
> issue is limited to jdk activation.)
> I have attached a simple test project to prove the issue. If you run {{mvn
> help:all-profiles}}, you can see that {{my.jdk16}} is not activated for the
> module _my-app_ (but it should).
> {noformat}
> [INFO] [help:all-profiles]
> [INFO] Listing Profiles for Project:
> com.mycompany.app:mvn-bug:pom:1.0-SNAPSHOT
> Profile Id: my.jdk16 (Active: true , Source: pom)
> Listing Profiles for Project: com.mycompany.app:my-app:jar:1.0-SNAPSHOT
> Profile Id: my.jdk16 (Active: false , Source: pom)
> {noformat}
--
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
