mirror of https://github.com/apache/maven.git
Updated the notes about the order of processing and a small problem with the conflation of duplicate checkingin getProjectMap
This commit is contained in:
parent
7c3052ddeb
commit
6e3f24babc
|
@ -183,12 +183,14 @@ public class DefaultMaven
|
||||||
//
|
//
|
||||||
// 5) Execute AbstractLifecycleParticipant.afterSessionStart(session)
|
// 5) Execute AbstractLifecycleParticipant.afterSessionStart(session)
|
||||||
//
|
//
|
||||||
// 6) Get reactor projects looking for read errors, and duplicate declarations
|
// 6) Get reactor projects looking for general POM errors
|
||||||
//
|
//
|
||||||
// 7) Create ProjectDependencyGraph using trimming which takes into account --projects and reactor mode. This ensures
|
// 7) Create ProjectDependencyGraph using trimming which takes into account --projects and reactor mode. This ensures
|
||||||
// that the projects passed into the ReactorReader are only those specified.
|
// that the projects passed into the ReactorReader are only those specified.
|
||||||
//
|
//
|
||||||
// 8) Create ReactorReader with the project map created in 7)
|
// 8) Create ReactorReader with the getProjectMap( projects ). NOTE that getProjectMap(projects) is the code that
|
||||||
|
// checks for duplicate projects definitions in the build. Ideally this type of duplicate checking should be part of
|
||||||
|
// getting the reactor projects in 6). The duplicate checking is conflated with getProjectMap(projects).
|
||||||
//
|
//
|
||||||
// 9) Execute AbstractLifecycleParticipant.afterProjectsRead(session)
|
// 9) Execute AbstractLifecycleParticipant.afterProjectsRead(session)
|
||||||
//
|
//
|
||||||
|
|
Loading…
Reference in New Issue