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

[jira-importer]

Brian Jackson opened MANTRUN-78 and commented

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.

---

Affects: 1.1, 1.2

Attachments:

• test.zip (5.63 kB)

Issue Links:

• MANTRUN-216 CLONE - Use of AntRun during clean phase fails multiproject with intermodule dependencies
  ("is duplicated by")
• MNG-3283 Plugins that require dependency resolution in early phases cause dependency resolution issue
  ("depends upon")

5 votes, 8 watchers

[jira-importer]

Carlos Sanchez Gonzalez commented

No error is provided but I guess it's same as MANTRUN-51

[jira-importer]

Brian Jackson commented

I disagree that it's a duplicate. The error and the way it exhibits itself is very different from MANTRUN-51.

Please run the test case I attached. The error you'll see is below. The only task in the antrun config is a simple echo command.

C:\test>mvn clean -Pbuild-failure
[INFO] Scanning for projects...
[INFO] Reactor build order:
[INFO] test
[INFO] test-b
[INFO] test-a
[INFO] ------------------------------------------------------------------------
[INFO] Building test
[INFO] task-segment: [clean]
[INFO] ------------------------------------------------------------------------
[INFO] [clean:clean]
[INFO] [antrun:run {execution: default}]
[INFO] Executing tasks
[echo] test
[INFO] Executed tasks
[INFO] ------------------------------------------------------------------------
[INFO] Building test-b
[INFO] task-segment: [clean]
[INFO] ------------------------------------------------------------------------
[INFO] [clean:clean]
[INFO] [antrun:run {execution: default}]
[INFO] Executing tasks
[echo] test
[INFO] Executed tasks
[INFO] ------------------------------------------------------------------------
[INFO] Building test-a
[INFO] task-segment: [clean]
[INFO] ------------------------------------------------------------------------
[INFO] [clean:clean]
[INFO] snapshot com.example.test:test-b:1.0-SNAPSHOT: checking for updates from
espn.releases
[INFO] snapshot com.example.test:test-b:1.0-SNAPSHOT: checking for updates from
espn.snapshots
Downloading: http://maven2.corp.espn3.com/archiva/repository/releases//com/examp
le/test/test-b/1.0-SNAPSHOT/test-b-1.0-SNAPSHOT.jar
Downloading: http://maven2.corp.espn3.com/archiva/repository/snapshots//com/exam
ple/test/test-b/1.0-SNAPSHOT/test-b-1.0-SNAPSHOT.jar
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Failed to resolve artifact.

Missing:

---

1. com.example.test:test-b:jar:1.0-SNAPSHOT

Try downloading the file manually from the project website.

Then, install it using the command:
mvn install:install-file -DgroupId=com.example.test -DartifactId=test-b -D
version=1.0-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file

Alternatively, if you host your own repository you can deploy the file there:

mvn deploy:deploy-file -DgroupId=com.example.test -DartifactId=test-b -Dve

rsion=1.0-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -Drepository
Id=[id]

Path to dependency:

1. com.example.test:test-a:jar:1.0-SNAPSHOT
2. com.example.test:test-b:jar:1.0-SNAPSHOT

---

1 required artifact is missing.

for artifact:
com.example.test:test-a:jar:1.0-SNAPSHOT

from the specified remote repositories:
espn.releases (http://maven2.corp.espn3.com/archiva/repository/releases/),
espn.snapshots (http://maven2.corp.espn3.com/archiva/repository/snapshots/),
central (http://repo1.maven.org/maven2)

[INFO] ------------------------------------------------------------------------
[INFO] For more information, run Maven with the -e switch
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 6 seconds
[INFO] Finished at: Thu Jul 17 15:02:43 EDT 2008
[INFO] Final Memory: 3M/6M
[INFO] ------------------------------------------------------------------------

C:\test>

[jira-importer]

Carlos Sanchez Gonzalez commented

Confirmed with Maven 2.0.9 and antrun 1.1 and 1.2

[jira-importer]

Florian Kolbe commented

I can also confirm this bug, tried maven 2.0.9, 2.0.10 and 2.1.0

[jira-importer]

Paul Gier commented

The problem is that the antrun plugin requires dependency resolution in order to create properties containing the paths to the dependencies. When you run "clean", the module jars are not available in the reactor and cannot be resolved. The same error can be seen by tying the antrun execution to an early phase like "validate". Unfortunately, this cannot be fixed in the antrun plugin, it would have to be fixed in Maven's dependency resolution (MNG-3283)

[jira-importer]

Adrián Boimvaser commented

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.

[jira-importer]

Michael Osipov commented

This issue has been auto closed because it has been inactive for a long period of time. If you think this issue still persists, retest your problem with the most recent version of Maven and the affected component, reopen and post your results.

[jira-importer]

Mark commented

Issue still exists with maven 3.6.0 and antrun plugin 1.8 in pre-clean phase.

[jira-importer]

Michael Osipov commented

Reopening per request.

[jira-importer]

Sylwester Lachiewicz commented

The solution, to switch to requireDependencyCollection, does't work here as we need paths to downloaded .jar to pass as properties to Ant.

https://issues.apache.org/jira/browse/MNG-3283?focusedCommentId=15962287&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-15962287