[MNG-4660] Use of --resume-from in multi-module project fails with missing inter-module dependencies

[jira-importer]

Brian Ferris opened MNG-4660 and commented

In a simple multi-module project with a parent pom "modules-parent", two sub modules "module-a" and "module-b", where B depends on A, I've not been able to get the Maven "--resume-from" feature to work.

Specifically, I expect:

mvn --resume-from module-b test

would resume execution of the "test" goal in "module-b". Instead it fails with a missing artifact error:

[INFO] Failed to resolve artifact.

Missing:

1. org.test:module-a:jar:0.0.1-SNAPSHOT

Why isn't Maven resolving the within-multi-module dependency? I've attached a simple project that reproduces the problem with Maven 2.2.1 and Maven 3.0-beta-1.

---

Affects: 2.2.1, 3.0-beta-1

Attachments:

• modules-parent.tar.gz (1.35 kB)

Issue Links:

• MNG-7099 Can not resume build without installing the artifacts
  ("is duplicated by")

• MNG-7527 Resolving inter-module dependencies does not work like expected
  ("causes")

• MNG-7024 Directory instead of file in an artifact

• MNG-6160 Forking process not always aware of reactor projects
  ("is depended upon by")

Remote Links:

• GitHub Pull Request #53
  
• GitHub Pull Request #54
  
• GitHub Pull Request #90
  
• GitHub Pull Request #91
  
• GitHub Pull Request #129
  
• GitHub Pull Request #325
  
• GitHub Pull Request #414
  
• GitHub Pull Request #416
  

Backported to: 4.0.0-alpha-2

5 votes, 4 watchers

[jira-importer]

Robert Scholte commented

--resume-from should only be adviced after a mvn install or mvn deploy, because it will look in the local repository for such dependencies.
There's room for improvement here if Maven could serialize/store the references to either the class-folder or the artifact of the past succesful builds if the total build fails, so Maven can pick them up when using -rf.
This would be nice to pick up as part of the incremental builds.

[jira-importer]

Wouter de Vaal commented

We are using an optimized automated build that uses resume-from. Resolving via install is not a good option, as we have multiple branches building the same code. So resolving locally would really help us.

[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 applies, retest your problem with the most recent version of Maven and the affected component, reopen and post your results.

[jira-importer]

Robert Scholte commented

reopening, still valid and fits in our goal to prefer verify over install

[jira-importer]

Robert Scholte commented

Fixed in ec92934bf08f11e8541e897c0f466f1f03c73a78 with integration test in 8c109b34977dc896698e9074e3656fa01f22b997
Thanks for the PRs!