[
http://jira.codehaus.org/browse/MNG-3530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=164723#action_164723
]
Brett Porter commented on MNG-3530:
-----------------------------------
I think I made the same mistake I may have made earlier - running "mvn clean
install" from the first instructions with the second project. It works if I run
the clover instrument command per the latter instructions.
> Regression: Properties get resolved before the LifeCycle is Forked.
> -------------------------------------------------------------------
>
> Key: MNG-3530
> URL: http://jira.codehaus.org/browse/MNG-3530
> Project: Maven 2
> Issue Type: Bug
> Components: General
> Affects Versions: 2.0.9
> Reporter: Nick Pellow
> Assignee: John Casey
> Fix For: 2.1.0-M1
>
> Attachments: MNG-3530.tar.gz, MNG-3530.zip
>
>
> Since Maven 2.0.9 -- If a plugin uses a forked lifecycle, then the project
> properties are resolved by maven before the lifecycle is forked.
> This means that the forked lifecycle has the non-forked lifecycle's values.
> This was not the case in maven prior to version 2.0.9, where properties were
> resolved at a much later time.
> For example - the attached sample project uses the Clover plugin with the
> xdoclet plugin. When {code}mvn clean install{code} is run under *Maven-2.0.8*
> you can see the following output:
> {code}
> [INFO] [xdoclet:xdoclet {execution: default}]
> [INFO] Initializing DocletTasks!!!
> [INFO] Executing tasks
> [echo] Build Dir: ${project.build.directory}/test.clover
> [INFO] Executed tasks
> {code}
> whilst *Maven 2.0.9* outputs:
> {code}
> [INFO] [xdoclet:xdoclet {execution: default}]
> [INFO] Initializing DocletTasks!!!
> [INFO] Executing tasks
> [mkdir] Created dir: /Users/niick/work/mvnclvr/src/it/mng/xdoclet/target
> [touch] Creating
> /Users/niick/work/mvnclvr/src/it/mng/xdoclet/target/test.clover
> [echo] Build Dir:
> /Users/niick/work/mvnclvr/src/it/mng/xdoclet/target/test.clover
> [INFO] Executed tasks
> [INFO] [resources:resources]
> {code}
> The fact the ${project.build.directory} property has been expanded already
> under 2.0.9, means that the forked lifecycle has the same value for that
> property.
> This new behavior will break any plugin which uses a forked lifecycle.
--
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
