So what's happening is, I'm activating a few profiles, yet the properties that are missing are set in an <activeByDefault> profile. It appears that the <activeByDefault> profile is either not activated or ignored.
If I turn on this profile (along with my other profiles), the properties are expanded properly. My plugin is simply loading some properties from a property file and pushing them into the mavenProject property listing. So two questions: 1 - do I need to do anything special to load all the properties defined in any activeByDefault profiles? 2 - What lifecycle goal should I bind my plugin to? -----Original Message----- From: EJ Ciramella [mailto:[EMAIL PROTECTED] Sent: Thursday, September 11, 2008 5:05 PM To: [email protected] Subject: Property access from a plugin If you have a set of properties set within a profile that is active by default, programmatically, how do you access them? If I do help:effective-pom, I can see that they are set and if I do help:active-profiles, I can see the profile is also active, just when I list the properties, the are not set. My plugin is defined as an aggregate plugin bound to process-sources (so POST initialize). mavenProject.getProperties() shows them as unset, any suggestions? --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
