You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Adrián Boimvaser (JIRA)" <ji...@codehaus.org> on 2012/11/22 14:19:13 UTC

[jira] (MANTRUN-78) Use of AntRun during clean phase fails multiproject with intermodule dependencies

    [ https://jira.codehaus.org/browse/MANTRUN-78?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=314191#comment-314191 ] 

Adrián Boimvaser commented on MANTRUN-78:
-----------------------------------------

What if there were an optional boolean parameter for choosing not to create properties containing the paths to the dependencies? Some people might need those properties but many could still run their ant tasks without them.
                
> Use of AntRun during clean phase fails multiproject with intermodule dependencies
> ---------------------------------------------------------------------------------
>
>                 Key: MANTRUN-78
>                 URL: https://jira.codehaus.org/browse/MANTRUN-78
>             Project: Maven 2.x Antrun Plugin
>          Issue Type: Bug
>    Affects Versions: 1.1, 1.2
>         Environment: Maven version: 2.0.8
> Java version: 1.5.0_12
> OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows"
>            Reporter: Brian Jackson
>         Attachments: test.zip
>
>
> Attaching the antrun plugin to the clean phase causes it to interfere with local dependency resolution for sibling projects. 
> An example is attached.
> The project consists of project 'test' with modules 'test-a' and test-b'.  'test-a' depends on 'test-b'.
> If you run "mvn clean" on the root POM, the clean succeeds.  
> If you run "mvn clean -Pbuild-failure" it fails.  

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira