Sahoo,
I think you need to add something to the reporting so we can exempt
certain cases in which GlassFish itself might not refer to an exported
package - and therefore it shows up as "unused" in the report - but
users writing their own OSGi modules would need to see the package and
therefore it must be exported.
Also, we will always have this, for example, for our container modules
which are loaded dynamically and therefore must export packages that
will be needed at runtime even though they might not be referenced at
build-time.
Or have I misunderstood something?
- Tim
On May 6, 2010, at 12:03 AM, Sahoo wrote:
> As discussed in the last engg. meeting, the link to the Wiki page I
> have created for this purpose is:
>
> http://wiki.glassfish.java.net/Wiki.jsp?page=OsgiPkgDepAnalyser
>
> Thanks,
> Sahoo
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>