Today I released the version 1.3.1 of the “Open File At Cursor” plugin. There are some new minor features, which proofed to be useful for myself and may be also useful for other Java developers.
Updates in 1.3.1:
- [Issue 18]: NPE when pressing CTRL in the diff dialog
Updates in 1.3.0:
- [Feature 12]: Support fully qualified classnames
- [Feature 14]: Search for classname in dependencies too (only works for dependencies with sources)
- [Feature 10]: Find files in same package but different source root
- [Issue 16]: Make the hyperlinking faster / use less IO
You can download it from http://plugins.netbeans.org/plugin/52349/open-file-at-cursor. The plugin is currently scheduled for verification for NB 8.0 and NB 7.4 and will be available from the plugin dialog within your NetBeans IDE within the next days (after verification).
As always please file issues and enhancements at https://github.com/markiewb/nb-resource-hyperlink-at-cursor/issues . Pull request are also appreciated. Thank you
In large Maven-based projects consisting of several high-level frameworks sooner or later there will come the time, when there are two versions of the same dependency in the classpath. For example: two versions of the same logging framework.
One approach to solve such ambiguity is to choose one of the versions (which is hopefully compatible) and to use it as an explicit dependency. Nevertheless other dependencies may still introduce other version as transitive dependencies. This may be caused by different groupIds, which will result in two similar named jar.
Once you got a candidate you can start finding all the possible sources of the dependency.
mvn dependency:tree -Dverbose -Dincludes=log4j:log4j
will show you the dependency-tree, but only the relevant excerpt. Using this information you can now add your exclusions to the affected pom.xml files.
Exclusions are configured via the exclusion-tag , which excludes specific transitive dependencies. For example:
By the way: Java IDEs can help you doing this.
After that you can make sure the faulty dependency versions will never ever be included again. This can be done using the maven-enforcer-plugin 
<!-- exclude all versions lower than 1.2.17-->