[ 
https://jira.codehaus.org/browse/MNBMODULE-148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jesse Glick closed MNBMODULE-148.
---------------------------------

    Resolution: Won't Fix

Anything like this would have to be filed on netbeans.org since it would be an 
API change in (I suppose) {{org.openide.modules}}. The Maven plugin change 
would then just follow the Ant harness change.

Since the NB module system only permits whole packages to be public, not 
individual classes, the annotation would need to be on {{package-info.java}}.

Some build-time additions to the public package list would still be necessary, 
because of modules which bundle third-party binary libraries.

> Class annotations for publicPackage
> -----------------------------------
>
>                 Key: MNBMODULE-148
>                 URL: https://jira.codehaus.org/browse/MNBMODULE-148
>             Project: Maven NetBeans Module Plugin
>          Issue Type: Improvement
>    Affects Versions: 3.6
>            Reporter: Johannes Boesl
>            Assignee: Jesse Glick
>            Priority: Minor
>
> It would be nice if I were able to specify which of my classes shall be 
> usable by other modules by using an annotation on those classes.
> The common way for maven-nbm is by using:
> <configuration>
>   <publicPackages>
>     <publicPackage>...</publicPackage>
>   </publicPackages>
> </configuration>
> Instead I can imagine of just putting '@NBM-Public-Class' or something like 
> that. Or with a package-annotation put a whole package public.
> When NetBeansPlatform project itself provides annotations for this case the 
> annotations are already in place an can be replaced with a simple 
> textprocessor.
> Since I am a big fan of the latest uses of annotations in NBP for me 
> introducing new annotations for other configuration of NBP is just beeing 
> consequent.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email


Reply via email to