dev@glassfish.java.net

Re: Heads up: gf-client.jar location change coming in 3.1 b29

From: Sanjeeb Sahoo <Sahoo_at_Sun.COM>
Date: Wed, 10 Nov 2010 13:51:12 +0530

Snjezana,

My understanding is lib/gf-client.jar can't be added to "common class
loader," which is used as parent loader for all application class
loaders. For lib/gf-client.jar not to be picked up by our "common class
loader," it has to have the following manifest metadata:

GlassFish-ServerExcluded true

See lib/javaee.jar for example.

Thanks,
Sahoo

On Wednesday 10 November 2010 05:08 AM, Snjezana Sevo-Zenzerovic wrote:
> As the result of the fix for issue https://glassfish.dev.java.net/issues/show_bug.cgi?id=8250 gf-client.jar has to be moved from glassfish/modules to glassfish/lib directory. This change is already checked in into trunk workspace and it will show up in next week's promoted build (i.e. b29).
>
> While appclient and package-appclient scripts have been updated to use new location, you will need to adjust any test setups which explicitly reference modules/gf-client.jar in the classpath. Note that I already updated any explicit references to modules/gf-client.jar in QL and devtests workspace (i.e. everything under https://svn.dev.java.net/svn/glassfish-svn/trunk/v2/appserv-tests/ ) but I may have missed something less obvious. Please let me know if you notice any issues.
>
> Thanks,
>
> Snjezana
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>
>