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.
We might want to have a hint you could set in the POM that would let the user make the final decision about preferSources; see the dummy use of Shade in [1] for example. Should take priority over ShadePluginDetector and osgi.ForeignClassBundlerImpl (i.e. position=0). [1] https://svn.codehaus.org/mojo/trunk/mojo/nbm-maven/nbm-maven-harness/pom.xml
Have another case where I am using <attachArtifact> from maven-antrun-extended-plugin, which I guess NB does not know about.
Created attachment 137814 [details] Background patch Preparatory patch.
Created attachment 137815 [details] Suggested patch Suggested patch. I can confirm in a debugger that it affects preferSources() on a project; unfortunately I have not yet been able to confirm that it produces the desired effect: 1. On nbm-maven-harness, even without this property set, if I delete the Shade plugin then nbm-maven-plugin scans OK. 2. On my proprietary project, whether this property is set or not, there are no errors in classpath scanning for the project using the library with a binary replacement, but source association does not work even though the *-sources.jar is in my local repo. These sound like bugs in the Java infrastructure but I am not sure what might be going on.
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