On Fri, Aug 5, 2011 at 4:11 PM, Anders Hammar <[email protected]> wrote:
> I guess [1] could give you some help. You would then do this in the > aggregator project. > Right, which is what I think you were saying was to be discouraged. But that page says that it is common practice. From the cited link: It is common practice to create an assembly using the parent POM of a > multimodule build. At times, you may want to ensure that this assembly also > includes the source code from one or more of the modules in this build. > Which is it? :-) > 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. > Sure; I understand this part. > Then just execute "mvn deploy" and the source archive will be deployed if > you configure the assembly plugin correctly. > Oh, so the assembly plugin will take care of marking the artifacts it produces in some magic way so that deploy will know about them? That would be handy indeed. Thanks, Laird
