Okay, so what I'm reading from this conversation is that you want to:
a. have a multimodule build b. wrap the <modules/> up in an assembly First question: why not do the build and assembly all in one step? Why install the modules to a repository first? When the assembly descriptor references a <moduleSet/> it's talking about a set of <module/> entries in the current POM. If it's including binaries of those modules, they will have to be built. If you're not doing a true multimodule build here, why not use a dependencySet instead? Dependencies are resolved from the repository, not modules. Finally: When you perform this multimodule build targeting different JVMs, how do you specify the classifiers to use in tagging the output jars? Is this - and the compiler configuration that I assume you're changing too - injected into the build(s) via profile, or...? -john On 8/8/06, mike7 <[EMAIL PROTECTED]> wrote:
Aggregator project = parent pom that refers to modules to be built. Are you using maven 2???? -- View this message in context: http://www.nabble.com/Assembly-madness...-tf2070731.html#a5713721 Sent from the Maven - Users forum at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
