Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
3.0-beta-2
-
None
Description
Currently, dependency resolution happens only at the beginning of a project build and then only for the current project. This means if the current project happens to bind an aggregator into its lifecycle which forks the lifecycle in a reactor build, any forked project not previously built during the main build will have its dependencies unresolved.
Attachments
Attachments
Issue Links
- is duplicated by
-
MSITE-497 Dependencies not included classpath for multi-level projects when forking reporting
- Closed