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.
Summary: | Required Projects contains modules from previously-opened projects | ||
---|---|---|---|
Product: | projects | Reporter: | _ gtzabari <gtzabari> |
Component: | Maven | Assignee: | Milos Kleint <mkleint> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | ||
Priority: | P3 | ||
Version: | 7.4 | ||
Hardware: | PC | ||
OS: | Windows 7 | ||
Issue Type: | DEFECT | Exception Reporter: |
Description
_ gtzabari
2013-10-03 19:41:23 UTC
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. |