I just committed a change that builds pe/nucleus/nucleus-base in
somewhat different ways than before.
The main change is the creation of the glassfish/web directory, which
hosts webtier modules and its dependency jar files. The exact
computation logic is bit too long to describe here, but just FYI the
following ls output shows what file is where.
> % ls ../web
> activation-1.1.jar ejb-api-3.0.jar mail-1.4.1ea-SNAPSHOT.jar
> admin-util-10.0-SNAPSHOT.jar gf-web-connector-10.0-SNAPSHOT.jar modeler-1.1.jar
> annotation-framework-10.0-SNAPSHOT.jar hk2-0.2-SNAPSHOT.jar persistence-api-1.0b.jar
> ant-10.0-SNAPSHOT.jar jasper-jsr199-9.1.jar pwc-10.0-SNAPSHOT.jar
> ant-1.7.0.jar javaee-5.0.jar security-api-1.1.jar
> ant-launcher-1.7.0.jar javaee-core-10.0-SNAPSHOT.jar servlet-api-2.5.jar
> auto-depends-0.2-SNAPSHOT.jar jaxb-api-2.0.jar sjsxp-1.0.jar
> auto-depends-plugin-0.2-SNAPSHOT.jar jaxrpc-api-1.1.jar stax-api-1.0-2.jar
> beanutils-1.6.1-20070314.jar jaxws-api-2.0.jar tiger-types-1.0.jar
> collections-2.1.jar jms-api-1.1.jar transaction-api-1.1.jar
> config-0.2-SNAPSHOT.jar jsp-api-2.1.jar war-util-10.0-SNAPSHOT.jar
> connector-api-1.5.jar jsr173_api-1.0.jar webtier-10.0-SNAPSHOT.jar
> deployment-api-1.2.jar jsr181-api-1.0-MR1.jar xercesImpl-2.8.1.jar
> digester-1.5.jar jsr250-api-1.0.jar xml-apis-1.3.03.jar
> dol-10.0-SNAPSHOT.jar logging-api-1.0.4.jar
> [~/ws/gfv3/v3/distributions/pe/target/glassfish/modules_at_bear]
> % ls .
> admin-cli-10.0-SNAPSHOT.jar deployment-api-1.2.jar jruby-complete-1.1b1.jar
> ant-1.5.jar gf-jruby-connector-10.0-SNAPSHOT.jar jsr223-api-1.0.jar
> asm-2.2.3.jar gf-phobos-connector-10.0-SNAPSHOT.jar junit-4.3.1.jar
> asm-analysis-3.0.jar glassfish-10.0-SNAPSHOT.jar kernel-10.0-SNAPSHOT.jar
> asm-commons-3.0.jar glassfish-api-10.0-SNAPSHOT.jar logging-api-1.0.4.jar
> asm-tree-3.0.jar grizzly-framework-1.7.0.jar persistence-api-1.0b.jar
> asm-util-3.0.jar grizzly-http-1.7.0.jar phobos-runtime-0.5.10.jar
> auto-depends-0.2-SNAPSHOT.jar grizzly-http-utils-1.7.0.jar portunif-1.7.0.jar
> backport-util-concurrent-2.0_01_pd.jar grizzly-jruby-1.7.0.jar servlet-api-2.5.jar
> bsf-2.3.0.jar grizzly-module-1.7.0.jar sjsxp-1.0.jar
> cli-framework-10.0-SNAPSHOT.jar grizzly-rcm-1.7.0.jar stax-api-1.0-2.jar
> common-util-10.0-SNAPSHOT.jar hk2-0.2-SNAPSHOT.jar tiger-types-1.0.jar
> config-0.2-SNAPSHOT.jar javadb-10.2.2.1-20070823.jar
> config-api-10.0-SNAPSHOT.jar jline-0.9.91.jar
You'll see some duplicates here and there, and some of them are by
design, but there could be some bugs --- possibly either in the
distribution assembly process, or in the POM files. If you find
something that shouldn't be there, please let me know.
Some of the issues are known --- for example, junit ends up in here
because jline depends on it incorrectly. HK2 ends up in both directories
because they are not modules by themselves and people depend on it directly.
Also, AFAIK the web/ directory is not added to the HK2 world as a
repository, so no modules from there are loaded when v3 runs, as it
stands today.
I need to check with Jerome if he intends to fix this by updating
core/bootstrap/pom.xml to include ../web, or by some other means.
--
Kohsuke Kawaguchi
Sun Microsystems kohsuke.kawaguchi_at_sun.com