maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nick Pellow (JIRA)" <j...@codehaus.org>
Subject [jira] Commented: (MNG-3530) Regression: Properties get resolved before the LifeCycle is Forked.
Date Thu, 15 May 2008 00:41:27 GMT

    [ http://jira.codehaus.org/browse/MNG-3530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=134877#action_134877
] 

Nick Pellow commented on MNG-3530:
----------------------------------

Hi Shane, 

No need for verification. I mistakenly left a reference to the clover maven plugin. This is
not needed to reproduce the bug.
Please remove the plugin configuration from the pom.xml and try again.

I've attached the archive again, with the plugin removed.

Cheers,
Nick

> 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.0.10
>
>         Attachments: MNG-3530.tar.gz
>
>
> 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

        

Mime
View raw message