| Item |
Type |
Comment |
Response |
| 4.5.1.2 |
Clarification |
What about files that are not OSGi bundles? e.g., scripts, docs, etc? How are they mapped to IPS packages? |
Complete package manifests will be provided as separate document, one pager intends to provide only high level overview of package/functionality mapping. |
| 3.1 |
Clarification / Enhancement |
On Ubuntu, when certain packages are not installed, are users told what package to install when they run the missing commands? e.g., let's say, webservice package is not installed, but it is available in repository. When user runs wscompile, what is the response? Is it "command not found, " or something like "this package is not installed yet, please run sudo apt-get glassfish-ws-pkg." |
Ubuntu distribution is now outside of the scope of one-pager since it will be post-Prelude deliverable. However, providing stub scripts would be good feature to have. |
| 4.5.1.1 |
Clarification |
Why do we need a bin dir under <install-dir>? |
Main purpose of this unified bin directory is to enable user to add only one single location to their PATH and have access to all commonly used utilities for any |
| 4.5.1.1 |
Clarification |
On what basis do we decide what goes in <install-dir>/bin? |
Guideline is to add any utility which is expected to be commonly invoked by end user there. |
| 4.5.1.1 |
Clarification |
Why can't we retain backward compatibility by having j2ee.jar, javaee.jar and appserv-ext.jar in <install-dir>/glassfish/lib dir? Not having them will cause major compatibility issues for existing build scripts including our QA scripts. |
Accepted, we'll add stub jar files in the lib directory. |
| 4.5.1.1 |
Clarification |
Why do we not create directories like <domain-dir>/lib/ext, <domain-dir>/classes? |
Accepted, domain file layout updated accordingly. |
| 4.5.1.2 |
Clarification |
Did you mean only web distribution when you said GlassFish v3 build? GlassFish v3 build also produces a full distribution, a.k.a. glassfish bundle. |
For Prelude release full glassfish bundle will not be externaly available. GF packager module will produce all the packages listed in one-pager and some of them will be shipped as part of initial distribution(s) while others will be made available only through update center. |
| 4.5.1.2 |
Correction |
Before finalising the package to bundles mapping, every module owners must be asked to submit their bundle list. This will go a long way in success of our product. We should not use the current bundle list for finalising the package list. |
Accepted. It is now noted that bundle list is snapshot and up-to-date mapping will be provided and maintaned separately in product manifest documents. |
| 4.5.1.2 |
Clarification |
Can we divide "Common utilities and components" package to two packages, viz: "Common utilities" and "Common components?" |
glassfish-common package is now separated into multiple functional areas which should implicitly address this. |
| 4.5.1.2 |
Correction |
org.glassfish.connectors should be moved to their own package called JCA |
Accepted, glassfish-jca package has been defined. |
| 4.5.1.2 |
Comments |
I think we have too many packages right now, at least in very early stage of the product. Since packages are public interfaces of the product, it will be difficult to remove any later. Should we have fewer, coarse-grained packages, each organised as per functional area to begin with? Then later on, we can divide them into smaller ones if we like? e.g., I would like to see something like this: glassfish-nucleus, glassfish-admin, glassfish-web-support, glassfish-ejb-support, glassfish-jdbc, glassfish-jca, glassfish-javaee, glassfish-docs |
Care was taken to define packages which will not have to be removed later although it is possible to further split some of them. Current package boundaries are designed to accomodate multi-tier installations once we introduce clustered environment and to accomodate proposed product distributions. We can always define package groups or wrapper packages to provide better user experience in Update center UI, so that would mitigate concerns about package number. |
