On Thu, Jul 10, 2008 at 5:43 PM, Raymond Feng <[EMAIL PROTECTED]> wrote:
> Hi, > > Let me take the two prototypes to build the "Collection" and compare them > aspect by aspect. > > 1) Aggregated jar: > http://svn.apache.org/repos/asf/tuscany/java/sca/modules/scdl4j/pom.xml > 2) Feature/Distro: > http://svn.apache.org/repos/asf/tuscany/sandbox/sebastien/distribution/base/pom.xml > > a. How is it declared as a maven module? > 1. Create a jar module, add the contained modules as dependencies, and use > the share plugin to aggregate/merge artifacts from the modules into the > target jar. Fairly-complicated exclusion filters and transformers have to be > defined. > 2. Create a pom module, add the contained modules as dependencies, add the > descriptor for the assembly and use the assembly plugin to assemble the > modules in a fairly-straightforward way. The distro can also contain related > samples. > > b. What will be produced? > 1: An aggregated jar that physically contains all the classes from the > modules and merged resource files. > 2: A zip or tar.gz that contains the modules as original jars in the > zip/tar.gz. > > c. How to declare dependency to reference them in maven? > 1: Declare a dependency to the new jar (Will the contained modules be > pulled in as transitive dependencies in addition to the aggregated jar?) > 2. Declare a dependency to the new pom (The contained modules will be > pulled in as transitive dependencies) > > d. How to use them in non-maven? > 1. Add the new jar to the classpath > 2. Unzip the zip/tar.gz so that all the contained modules will be on the > classpath (or use our ant generator, or mvn dependency:copy-dependencies to > copy the jars over) > > e. How to use them in OSGi? > 1. The new jar becomes a new bundle and it needs to merge the MANIFEST.MF > from the contained modules. (How do we deal with the import/export, > versioning?) > 2. The contained modules are the bundles, no new bundles are introduced. > > f. Can two collections contain the overlapping modules? > 1. No (AFAIK from Ant's response) > 2. Yes > > g. How to overlay the collections into an existing installation? > 1. Add the new jar assuming there are no duplicate > 2. Unzip the distro and either overwrite or ignore the duplicate modules > during the unzip > > h. Footprint > 1. It might pull in extra stuff not required, for example, to support WS, > we need to pull in scdl4j.jar which contains models for EJBs or BEPL. > 2. Can be potentially the bare minimum if we declare the feature/distro in > a fine-grained fashion. > > Please help to complete the list and correctly judged. > > I'm not ignoring this, just waiting to see what the request for user feedback on the user lists shows up. ...ant
