Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Duplicate
-
2.0.9
-
None
-
None
-
Windows, JDK 1.6.0_07
Description
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).
[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)
Attachments
Attachments
Issue Links
- duplicates
-
MNG-3228 Maven profile activation does not work when profile is defined in inherited 'parent' pom
- Closed