Dear John,
John Casey-3 wrote:
>
> Okay, so what I'm reading from this conversation is that you want to:
>
> a. have a multimodule build
> b. wrap the up in an assembly
>
YES ;-)
John Casey-3 wrote:
>
> 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 it's talking about a set of entries in
> the current POM. If it's including binaries of those modules, they will
> have
> to be built.
>
Not all modules are necessary to build one application. During the assembly
step, we'd like to have multiple assembly descriptors to build various
applications (and cherry pick the appropriate modules and their
corresponding dependencies).
John Casey-3 wrote:
>
> If you're not doing a true multimodule build here, why not use a
> dependencySet instead? Dependencies are resolved from the repository, not
> modules.
>
Thanks for the tip.
If dependencies are resolved from the repository, then why is maven trying
to recompile everything? Is there a flag to tell maven to just do assembly?
John Casey-3 wrote:
>
> 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...?
>
It is set by profile. There is a profile for the platform (j2me, j2se etc).
Then I set the classifier as ${platform}. This generates
myJar-1.0-SNAPSHOT-${platform}.jar.
I tried with the dependencySet as follows:
bin
jar
false
com.toto.myApp:apps
/
true
runtime
junit:junit
Well, it doesn't produce anything in the jar. If I use moduleSets then it
works but it doesn't exclude junit.
Thanks for your help!
--
View this message in context:
http://www.nabble.com/Assembly-madness...-tf2070731.html#a5714323
Sent from the Maven - Users forum at Nabble.com.
