[ http://jira.codehaus.org/browse/MNG-542?page=all ]
Brett Porter updated MNG-542:
-----------------------------
Description:
For example pom.build.outputDirectory (classes directory) should inherit from
pom.build.directory. Same for all properties that are used to generate build
data.
Why? Becasue otherwise it's downright impossible to change the location of the
target directory (pom.build.directory) as you don't know beforehand all the
plugins that are part of the lifecycle and how many properties they each have
and their name.
For example in the clover plugin I need to set the target dir to another
location so that main build data is not compromised. I can't do it as I can't
controll all the properties that could possibly exist. I'd just like to set the
pom.build.directory to a new value and be done with it.
was:
For example pom.build.outputDirectory (classes directory) should inherit from
pom.build.directory. Same for all properties that are used to generate build
data.
Why? Becasue otherwise it's downright impossible to change the location of the
target directory (pom.build.directory) as you don't know beforehand all the
plugins that are part of the lifecycle and how many properties they each have
and their name.
For example in the clover plugin I need to set the target dir to another
location so that main build data is not compromised. I can't do it as I can't
controll all the properties that could possibly exist. I'd just like to set the
pom.build.directory to a new value and be done with it.
Fix Version: 2.0-beta-1
Environment:
I'm not sure what the correct solution here is just yet, but it requires
investigation
> Allow properties to inherit from other properties
> -------------------------------------------------
>
> Key: MNG-542
> URL: http://jira.codehaus.org/browse/MNG-542
> Project: Maven 2
> Type: Wish
> Components: maven-core
> Versions: 2.0-alpha-3
> Reporter: Vincent Massol
> Fix For: 2.0-beta-1
>
>
> For example pom.build.outputDirectory (classes directory) should inherit from
> pom.build.directory. Same for all properties that are used to generate build
> data.
> Why? Becasue otherwise it's downright impossible to change the location of
> the target directory (pom.build.directory) as you don't know beforehand all
> the plugins that are part of the lifecycle and how many properties they each
> have and their name.
> For example in the clover plugin I need to set the target dir to another
> location so that main build data is not compromised. I can't do it as I can't
> controll all the properties that could possibly exist. I'd just like to set
> the pom.build.directory to a new value and be done with it.
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
