Aggregate third party report fails on multimodule maven that has module with cross dependencies

[nfalco79]

We are performing a release mvn release:prepare release:perform on a multimodule maven project.
Some module depends from other modules. The typical scenario is:
parent
|->model
|->client (depends from model)
|->web (depends from model)

The release plugin change the version and run a clean verify in all pom.xml after that run deploy site:deploy goals. The aggregate-add-third-party mojo run on parent project and to resolve all dependencies of children modules. It fails when one of child module depends on other child (web -> model) because aggregate-add-third-party is not able to resolve the child module with the new version since it has been never installed.

[ppalaga]

Thanks for the test. A fix is welcome as well.

[ppalaga]

@nfalco79 describes a workaround in #318 (comment) :

Change the preparationGoals of the mave-release-plugin from it default value (clean verify) to clean install so that when the release plugin run the second phase (perform) deploy site:deploy than the site generation of the parent project has jars of submodules available in the local m2.