Jean-Sebastien Delfino wrote:
Mike Edwards wrote:
Jean-Sebastien,
I was one of the nay-sayers way back.
But I've changed my mind. Let's try this out.
I still think that it would be useful to have install scripts that
would deal with popular runtime combinations (Geronimo, Tomcat, etc).
But your approach here will give us some "smal and simple" packages
for folk who are doing "small and simple" stuff.
+1 to put it into trunk.
The build scripts are already in trunk under distribution/features.
+1 to put it into the build too.
To build all packages run mvn in distribution/features.
To build package X run mvn in distribution/features/X.
To build a package and the modules it depends on run mvn -Pmodules.
Hope this helps.
I've made the following improvements to these packages:
- updated them to match the new or renamed modules in trunk
- used Maven assembly component descriptors for declarations shared by
multiple packages
- the packages are smaller as they don't duplicate anymore the jars from
the core package, and the sample modules exclude the binary files
- added shell scripts to help maintain the Maven descriptors, they
should be easy to convert to a Maven plugin (as they just wrap the Maven
dependency:list plugin:goal).
I've also started to test the latest OSGi support and I'll try to create
a similar package for it.
--
Jean-Sebastien
