In a module suite I have a library wrapper module for an existing plain Java project. I hooked them
up as described in method 1 at http://wiki.netbeans.org/DevFaqWrapperModules
So far all works fine: I have code-completion with javadoc and go-to-source when referencing my-project.
Now I want to rename a method in the plain Java project. Or I want to find its usages. Unfortunately
this does not work for references of the library in the module suite but only in dependent plain
Java projects. On the mailing list I was told that there's no way: the Library Wrapper "breaks" the chain of references.
Even the other way round would make sense. I have plain Java projects which depend on a couple of jars defined and built
by modules from a NetBeans module suite. I want refactoring to respect usages of the modules's classes in the plain Java
Method #2 is likely better; netbeans.org projects routinely use it. Method #1 is untested AFAIK.
*** This issue has been marked as a duplicate of 70894 ***
Do you mean that using method 2 I will get support for refactoring?
You should. I haven't tried recently.
In NetBeans IDE Dev (Build 200808241401) refactoring works (see issue 70894). Even the other way round plain Java
projects which depend on a couple of jars defined and built by modules from a NetBeans module suite are taken into
account when refactoring classes in the modules if the plain java projects directly depend on jars in build/cluster/modules.