I'll take a peek, thanks Jeremy
On 06/10/06, Jeremy Boynes <[EMAIL PROTECTED]> wrote:
On IRC Kelvin mentioned possibly re-jigging the SDO distribution format to include the assembly phase in the parent pom. The idea was that would make it easier to aggregate things like JavaDoc across the modules. I've taken a swag at this in my sandbox: https://svn.apache.org/repos/asf/incubator/tuscany/sandbox/jboynes/sdo This builds two ways: one to produce local artifacts, the other to produce a distribution. The first way is what we had before and allows you to build SDO as part of a larger reactor build (i.e. what we do when we build sdo, das and sca together). The default goal is "install" set by the reactor and that puts the binary jars in your local maven repo as usual. You can run this from the command line using "mvn package" or "mvn install" The second way does that, followed by a packaging step. That build aggregate javadoc across the modules (which is a slow step) and then builds the distribution bundles. This is intended to be run just to cut the release. You run this with "mvn package javadoc:javadoc assembly:assembly" and it: * builds and tests the jars as usual * generates javadoc aggregated across all the sdo modules * builds zip and tgz archives containing legal, jar files, the sample source and the javadoc - we can fine tune this as needed Kelvin, can you give this a go and see if it's what you want in the distro. Any other comments? Is this something we might want to do for DAS and SCA as well? -- Jeremy --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
