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.
Or make API in org.netbeans.modules.java.api.common stable. It is hard to reuse anything from Java project support if you are not in nb.org module universe. It would be nice to add org.netbeans.modules.android.project there.
As far as I remember Tomáš believes that certain parts of the module are not ready for production. The best solution in this case would be to split the module in two. Either: 1. create new module, make it stable and friend of existing one and extract there useful APIs that will delegate to the old friend API 2. create new module and move there the functionality that is not ready for production. Update all friends to depends also on the new module. Make the API left in the old module public.
Agree with Jarda
Why is Jarda's comment blocking this? If you add another friend module and later realize that you need a significant change then you can bump the major version version in module name, 3rd party module(s) will be broken until they receive update and vast majority of friends can be fixed in NB.org source tree. At least for Android stuff I am ready accept such bargain to be able to reuse the code. There are already 23 friend modules including Groovy and Scala.
Workaround: https://bitbucket.org/jglick/yenta
As the stabilisation of the project APIs was not approved for NB 7.3 I will at least add the org.netbeans.modules.android.project as a friend.
Fixed jet-main e5f8d243477e
Integrated into 'main-golden', will be available in build *201301050001* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main-golden/rev/e5f8d243477e User: Tomas Zezula <tzezula@netbeans.org> Log: #195931:Make org.netbeans.modules.android.project friend of Java Common Project API