> > 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? :-) >
I believe I wrote that *I* think that creating a separate module is better. I did not write that page. :-) Anyhow, I would say that normally it's better to create a separate module. But sometimes that would not work, which it doesn't I think for your use case. Maven's artifacts are per project, but your working on the full tree of modules/projects which calls for hacks... 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? > Yes. There's a configuration option for this which is true (attach as artifacts) by default. Convention over configuration... /Anders
