In the process of porting our NetBeans RCP app to maven and nbm-maven-plugin, I've noticed errors like this:
Project uses classes from transtive module org.netbeans.api:org-openide-nodes:jar:RELEASE68 Now, I understand why this error is emitted -- transitive dependencies must be explicitly stated in the netbeans module system, so there's no problem here. My *real* question is: these error are emitted even when the module usage in question occurs on *non-Java* code. A quick look at the nbm-maven-plugin source associated with this verification stage gives me the impression that the plugin is doing an analysis of the classfiles in target/classes, etc., rather than looking at source code. Can someone confirm this, or correct me on this point? If this is the case, then I'm absolutely thrilled -- compared to the NetBeans RCP ant process and the NB IDE, this would guarantee a degree of safety when programming with non-Java languages (which is the typical case here) that is not available otherwise. Thanks, - Chas -- View this message in context: http://old.nabble.com/Extent-of-dependency-analysis-performed-by-nbm-maven-plugin-tp26819020p26819020.html Sent from the mojo - user mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
