Description
Currently, if you try to run release:prepare on a multimodule project after removing any of that build's artifacts from the local repository, it will fail. Investigate why release:prepare needs the multimodule artifacts installed in the local repository before it can succeed.
To reproduce, comment the following line in it2002/test.sh:
mvn clean install
NOTE: This may have to do with the version resolution code, which is used to resolve SNAPSHOT versions.
Attachments
Issue Links
- is duplicated by
-
MRELEASE-330 target release:prepare fails for multiproject if cross project dependencies exist
- Closed
-
MRELEASE-102 Preparation goals 'clean integration-test' not sufficient for plugin-projects
- Closed
-
MRELEASE-228 release:prepare should not require multimodule artifacts to be in the local repository
- Closed
- is related to
-
MRELEASE-240 release-pom.xml does not contain <dependencies> and <dependencyManagement>
- Closed
-
MNG-4331 Add new requiresDependencyCollection mojo feature (with corresponding annotation) to grab dependency tree without files
- Closed
- relates to
-
MRELEASE-388 @requiresDependencyResolution on prepare mojo causes build to look for its own dependencies
- Closed
-
MRELEASE-62 Option not to run install phase during realease:prepare
- Closed
-
MRELEASE-326 Doens't resolve multiproject dependencies properly
- Closed