One of the fundamental principles that Maven operates on is the 1:1 association of POMs to primary output artifacts (not counting special assemblies, source, or javadoc jars). If you want, you might be able to construct a set of POMs that all reference the same source directory, and setup compiler excludes configurations such that each POM generates a jar based on a different subset of the sources in that single directory...
On 7/27/06, Alexis Midon <[EMAIL PROTECTED]> wrote:
Hi all, I'm currently migrating a big project from Ant to Maven. I have exploded the source code in modules as much as possible but for legacy reasons I want one of them to generate N output jars (instead of a single one). My question is How can I do that? I have several leads but some questions remain. Here they are : 1. add to package phase an antrun plugin to create the desired jars, but then the underlying question is: how to disable the 'jar:jar' goal during this phase? 1bis. use the assembly plugin to build several jars, sounds quite cumbersome and not better than the ant plugin solution. 2. is there a way to make the jar plugin generate several jars? Thanks for your help! Alexis
