I think this is a really cool idea.... I tried to do it for my project but unfortunately I couldn't find a way to reference the assembly of the subModule in the moduleSet of the parent module. The submodule assembly gets set as an 'attached' artifact and not the main one.. by the <binaries> tag in the moduleSet only supports the main modules. If we could add the classifier's on this would work very well I think!
Did you find an answer to this question? I am wanting to pull together our build so that we have everything that is needed in one place for easy deployment: ear files, zips of client applications, all the stuff I have previously assembled and is stored in the repository. In the assembly descriptor - moduleSet doesn't appear to be the answer as it looks like this is the modules from the pom. - repositories looks like it could be, but the documentation is thin and the code isn't helping me understand it any easier. All I've managed to do is to get a copy of the poms and jars out of the repository (not the assembled archives) My file layout looks like: ROOT - pom.xml - module1 - modulen - build - pom.xml Where the build/pom.xml will contain the assembly of everything that is needed from the other modules. I don't think putting the assembly plugin and descriptor in the ROOT/pom.xml is correct as then it will be inherited by all the modules. So the correct place to put together an aggregation is build/target. Any one else doing this and have some hints? Cheers Bae --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
