I guess [1] could give you some help. You would then do this in the aggregator project.
If you want it as part of the build you need to bind the plugin goal to the Maven lifecycle. Basic Maven stuff, Google or a Maven book is your friend. Then just execute "mvn deploy" and the source archive will be deployed if you configure the assembly plugin correctly. /Anders [1] http://maven.apache.org/plugins/maven-assembly-plugin/examples/multimodule/module-source-inclusion-simple.html On Fri, Aug 5, 2011 at 21:57, Laird Nelson <[email protected]> wrote: > On Fri, Aug 5, 2011 at 3:23 PM, Anders Hammar <[email protected]> wrote: > > > > I'd like to set up a plugin declaration to use the > maven-assembly-plugin > > to > > > put together a kind of standalone uber-distribution from the root. > > > > In my opinion it's much better to put this in a separate module. > > > > I sort of see what you are talking about, but if I want the distribution to > include (say) source code from all of the aggregator's modules, how would > the separate module come up with a list of modules? Wouldn't I be > repeating > the list of modules somewhere? > > When executing assembly:single you will not be executing the build > > lifecycle > > (and thus building all modules) but just execute that plugin goal. > > > I see. > > > > Shouldn't > > be any problem then, but understand that it's probably not the Maven way > as > > the assembly artifact being built will not be deployed to the repo. > > > > Oh! OK; I didn't see an assembly:deploy or anything like that. What would > you suggest? > > Thanks, > Laird >
