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.

Bug 166836 - GlassFish platform library size is huge
Summary: GlassFish platform library size is huge
Status: RESOLVED FIXED
Alias: None
Product: serverplugins
Classification: Unclassified
Component: GlassFish (show other bugs)
Version: 6.x
Hardware: All All
: P3 blocker (vote)
Assignee: Vince Kraemer
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-06-10 09:52 UTC by Petr Jiricka
Modified: 2009-07-21 18:51 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Petr Jiricka 2009-06-10 09:52:39 UTC 
1. Go to New Web Project wizard
2. Check "Use dedicated folder for storing libraries"
3. On the next panel, choose GF v3 as the target server and check "Use dedicated library folder for server JAR files"
4. Complete the wizard

The wizard creates the "GlassFish_v3" library folder, which is >20 MB in size. The biggest culprits are
webservices-osgi.jar, jaxb-osgi.jar and jsf-impl.jar. Are these jars really needed for compiling user code? If they are,
could they be split up so only the API part is included, not the implementation part? (This may be a request for
GlassFish itself, rather than the plugin.)
Comment 1 Petr Jiricka 2009-07-07 21:14:33 UTC 
I just saw a suggestion in a private e-mail to use modules/endorsed/jaxb-api-osgi.jar and
modules/endorsed/webservices-api-osgi.jar, which are much smaller.
Comment 2 Quality Engineering 2009-07-08 05:35:16 UTC 
Integrated into 'main-golden', will be available in build *200907080200* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress)
Changeset: http://hg.netbeans.org/main-golden/rev/a835aeeef832
User: Vince Kraemer <vkraemer@netbeans.org>
Log: #166836: prefer smaller api jars if they exist
Comment 3 Petr Jiricka 2009-07-08 11:52:30 UTC 
I tried the behavior in the latest build, and strangely, webservices-osgi.jar and jaxb-osgi.jar are still added, in
addition to the smaller API-only jars.

Next, other non-API jars that are included in the v3 platform right now are jsf-impl.jar and jstl-impl.jar. While these
are not needed for compiling user code, they need to be on the classpath: I just discussed with Marek Fukala (cc'ed)
that they contain tld files, and the JSP editor needs to see these jars on classpath in order to provide code completion
and other features for the tag libraries. So I would leave these two jar files in.
Comment 4 Vince Kraemer 2009-07-21 14:33:54 UTC 
I cannot reproduce the behavior that Petr talks about in http://www.netbeans.org/issues/show_bug.cgi?id=166836#desc4

I am closing this issue as fixed.

Open a new issue with steps to reproduce if you run into other problems with the library content.
Comment 5 Petr Jiricka 2009-07-21 18:51:03 UTC 
I can still reproduce the subissue I reported, so I filed a new issue 168927. Could this be Mac-specific or something?