Create a separate project for the config. In Maven, one project = one artifact. Sure, you can create additional artifacts, but that's the golden rule.
/Anders On Tue, Nov 9, 2010 at 15:35, jon.mithe <jon.mi...@gmail.com> wrote: > > Thanks for the reply. Yeah that is what I am trying to achieve. So there > are no configuration files within the jars and I'm trying to keep the > configs in the extra folder on the side. As far as I'm aware maven can > only > produce one artifact from the module during the build, so the only way I > can > see it will work would be some sort of zip/jar with all the complied jars > inside + the extra config directories attached on the side. > > Trying to think of ways to simplify the build, but cant see any. > > Hmm. > > Thanks, > Jon > -- > View this message in context: > http://maven.40175.n5.nabble.com/Custom-assembly-of-multi-module-project-tp3256773p3256929.html > Sent from the Maven - Users mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > >
