I noticed recently that if I open a Maven parent project, now all of its child projects open automatically. I'm not sure I like that, but I might get used to it.
However, today I'm noticing that if I open one non-parent project which happens to also be in another project group, a bunch of other projects from that group (which may not be the one I'm working in currently) magically open. I can't believe this is a feature :-)
you must have triggered "Open required projects" checkbox in the project opening dialog.
related to issue 210465, for maven projects "subproject" is fairly ambivalent term, we have a deterministic implementation for pom packaging projects -> <modules>, but for other packaging it's based on local repository (GAV) linking. That's very confusing and counter-productive in cases of multiple checkouts, but I think jglick claimed we cannot remove for backward compatibility reasons.
issue 203222 also related.
Yup. Must have accidentally checked it.
Yeah, I think subproject computation that was part of the weirdness, since it seemed fairly random.
Maybe there should be an "I'm Feeling Lucky" button in the Open Project dialog? :-)
(In reply to _ tboudreau from comment #2)
> Yup. Must have accidentally checked it.
> Yeah, I think subproject computation that was part of the weirdness, since
> it seemed fairly random.
> Maybe there should be an "I'm Feeling Lucky" button in the Open Project
> dialog? :-)
The other issues suggest that the non-pom projects should get no "subprojects" computed when opening, under some other conditions having a list of projects my project depends on is useful though. So that's why we need the multiple API contracts