This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
This was originally reported by someone else (as far back as 2007) in bug #120298 but I've only now found a way to reproduce it: Product Version: NetBeans IDE Dev (Build 201309270002) Java: 1.7.0_40; Java HotSpot(TM) 64-Bit Server VM 24.0-b56 Runtime: Java(TM) SE Runtime Environment 1.7.0_40-b43 System: Windows 7 version 6.1 running on amd64; Cp1252; en_CA (nb) User directory: C:\Users\Gili\AppData\Roaming\NetBeans\dev Cache directory: C:\Users\Gili\AppData\Local\NetBeans\Cache\dev 1. Take a Maven project with sub-modules at NetBeansProjects/A 2. Copy it to NetBeansProjects/B 3. Open Netbeans with a clean userdir. 4. File -> Open Project 4. Select project A. Notice that "Required Projects" lists the correct sub-modules. 5. Open project A. Close project A. 6. File -> Open Project 7. Select project B. Notice that "Required Projects" lists sub-modules from *both* A and B. Expected behavior: "Required Projects" should only list sub-modules from project B in step 7.
duplicate of issue 203222 the problem is the vague definition of subproject/required projects. in maven projects, pom projects get their subprojects from <modules> section while other packagings attempt to get the mapping from dependencies and match them against known project GAVs which are at the old location. *** This bug has been marked as a duplicate of bug 203222 ***
if you need to work with multiple sets of projects at different locations (multiple checkouts/clones) that share the same maven GAV, the working solution is to use project groups I believe. since 7.4 we reset the remembered GAV<->project dir mapping on project group change.
Wow. How long has *that* feature existed without me knowing about it?! I've never even heard of Project Groups before! Thanks for the head's up, I'll check it out. PS: The UI should be improved to highlight the existence of project groups somehow.