Thanks for this detailled reply.
I'll have to find an alternative to profiles. Ability to activate parent-POM
profiles from a POM would be really nice as it would enable pulling up lot's
of common configuration to corporate POMs.
For now, I'll use an archetype to add all the profiles to the
Unfortunately, this doesn't work in Maven 2.0.x.
The reason is that the profile activator actually uses
System.getProperty( project.target.jre ), not project.getProperties
().getProperty( project.target.jre ).
It's actually a fairly involved process to check the POM for
properties during
Hello,
I'd like to have a set of profiles in my corporate parent POM for various
maven usage. To enable them depending on projects I'd like to set a
property in the project POM to enable the profile :
example :
- corporate parent pom :
profile
idJava5/id
activation
