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.
[ BUILD # : 201306132201 ] [ JDK VERSION : 1.7.0_21 ] [win8x64] P4 because it's only for a specific dependencie. Create a maven java application from new project. edit pom => add <dependency> <groupId>org.apache.commons</groupId> <artifactId>commons-io</artifactId> <version>1.3.2</version> </dependency> go to the node matching the dependencies try remove: 1 dependencnies declared in parent project(s) were not removed.
I add a comment because this is not limited to the cited artifact. It's generalized to any artifact with relocation information Example for o.a.c:commons-io:1.3.2 <project> <modelVersion>4.0.0</modelVersion> <groupId>org.apache.commons</groupId> <artifactId>commons-io</artifactId> <version>1.3.2</version> <distributionManagement> <relocation> <groupId>commons-io</groupId> <artifactId>commons-io</artifactId> <message>https://issues.sonatype.org/browse/MVNCENTRAL-244</message> </relocation> </distributionManagement> </project>
the problem i likely caused by the fact that the effective, resolved model we have when constructing the dependency node only contains the relocated coordinates, not the original ones declared in the pom.
It may be interresting to have a flag on a dependency to show the relocated dependencies may be shown at node level may help user navigating upgrading artifact. May try to code that (if ok to have that in maven, and if no time rush) Regards Eric
any patches welcome, however AFAIK there's no way getting the relocation information from the Artifact or Dependency objects.
Created attachment 138207 [details] Add some infos in tooltip and html of dependencynode in case of relocation This is a little patch to show if an artifact is potentialy relocated. Basic idea is to compare coordinate of artifact and coordinate of dependency (after applying properties). This only for direct dependency. I try to make it simple for my point of view but I'm not sure of the performance, placement.
This old bug may not be relevant anymore. If you can still reproduce it in 8.2 development builds please reopen this issue. Thanks for your cooperation, NetBeans IDE 8.2 Release Boss