add support for ${basedir} property in profile activation
---------------------------------------------------------
Key: MNG-3140
URL: http://jira.codehaus.org/browse/MNG-3140
Project: Maven 2
Issue Type: Improvement
Components: Profiles
Affects Versions: 2.0.7
Reporter: nicolas de loof
Priority: Minor
The profile <activation> supports file based activation (exists/missing), but
properties are not supported to set the path.
My project use such a file-based activation, based on some generated-source
file :
<activation>
<file>
<missing>target/generated-sources/sql2java.tstamp</missing>
</file>
</activation>
My project is a module, and when I run the project from the parent project the
path is considered based on current dir (parent root) and not module root, so
the profile gets activated but shouldn't.
There's no support for properties in profile activation. I can understand this
as profile can themself change properties. Support for the ${basedir} property
could solve this issue. As this is a default maven property, it should be
immutable, so have no impact on profiles activations and other properties setup.
I would like to submit a patch, to enhance FileProfileActivator and replace
${basedir} with actual value in isActive, but I don't know where to get the
basedir value.
--
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
