[MNG-7646] Do not parse all projects in the reactor when building a subtree

[jira-importer]

Guillaume Nodet opened MNG-7646 and commented

---

Affects: 4.0.0-alpha-3

Issue Links:

• MNG-7647 The initial parsing of projects can be very slow

Remote Links:

• GitHub Pull Request #239
  
• GitHub Pull Request #962
  
• GitHub Pull Request #963
  

Backported to: 4.0.0-alpha-4

[jira-importer]

Maarten Mulders commented

I am still very much in doubt about this topic.

From a user point-of-view, I would expect Maven to "understand" that the subtree is part of a bigger project, and be able to at least resolve dependencies that live inside the same project tree. The idea to resolve that over a project-local repository (MNG-7629) sounds promising, but will that still work if Maven only parses a selection of the root project?

[jira-importer]

Guillaume Nodet commented

We'll see :-)
My point is that I want to focus on MNG-7629 first, and then see what can be done for this one. My main problem with the current state is the processing time when you want to build a single module in a big reactor. If MNG-7629 is solved, I don't have any other technical issues with parsing the whole reactor, so I would focus this issue on the processing time.