Maven 2 & 3

Profile with jdk activation is not inherited from parent pom

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Duplicate
  • Affects Version/s: 2.0.9
  • Fix Version/s: None
  • Component/s: Profiles
  • Labels:
    None
  • Environment:
    Windows, JDK 1.6.0_07
  • Complexity:
    Intermediate
  • Number of attachments :
    1

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)

Issue Links

Activity

There are no comments yet on this issue.

People

Vote (0)
Watch (2)

Dates

  • Created:
    Updated:
    Resolved: