You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Michael Osipov (JIRA)" <ji...@apache.org> on 2019/02/06 18:50:00 UTC
[jira] [Closed] (MANTRUN-216) CLONE - Use of AntRun during clean
phase fails multiproject with intermodule dependencies
[ https://issues.apache.org/jira/browse/MANTRUN-216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Osipov closed MANTRUN-216.
----------------------------------
Resolution: Duplicate
> CLONE - Use of AntRun during clean phase fails multiproject with intermodule dependencies
> -----------------------------------------------------------------------------------------
>
> Key: MANTRUN-216
> URL: https://issues.apache.org/jira/browse/MANTRUN-216
> Project: Maven Antrun Plugin
> Issue Type: Bug
> Affects Versions: 1.8
> Environment: Maven version: 3.6.0
> Java version: 11.0.2-open
> OS name: ubuntu 18 x86-64
> Reporter: Mark
> Priority: Major
>
> Can't re-open the original issue. The blocking issue MNG-3283 is said to be fixed. Does the antrun plugin have the nesseray update for the upstream fix to work?
> Attaching the antrun plugin to the clean phase causes it to interfere with local dependency resolution for sibling projects.
> An example is attached to MANTRUN-78 .
> 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 was sent by Atlassian JIRA
(v7.6.3#76005)