Details
Description
Create a new simple multimodule-project and call mvn validate at the toplevel. This leads to a build failure if none of the multimodule-artifacts are in your local repository.
Attached is a simple test project for reproducing this bug.
Attachments
Attachments
Issue Links
- depends upon
-
MNG-3283 Plugins that require dependency resolution in early phases cause dependency resolution issue
- Reopened
-
MECLIPSE-380 dependencies in multi-module may projects require a 'mvn install' before using
- Closed
- is duplicated by
-
MENFORCER-113 enforce goal should require dependency collection, not resolution
- Closed
-
MENFORCER-151 Artifact resolution not always on repository-chain
- Closed
- is related to
-
MENFORCER-304 Improve dependency resolving in multiple modules project
- Closed
-
MNG-4331 Add new requiresDependencyCollection mojo feature (with corresponding annotation) to grab dependency tree without files
- Closed
- relates to
-
MENFORCER-168 In a multi module project "bannedDependencies" rule tries to resolve project artifacts from external repository
- Closed