Currently, I think your best bet (as a user) is to create a post-jar callback that creates the additional JAR files for you. See the Integration document (section on Extending Maven's build system) for more info on callbacks.
Ideally (as a developer), you probably want to create a RMI plugin. This plugin could then be used to package up the individual JAR files. Please take a peek at the src/templates/build/plugins directory for examples. Specifically, the j2ee and struts plugins. If you decide to go down this route, please feel free to post your questions to the dev-list. Thanks! Pete On Wed, May 15, 2002 at 02:07:47PM +0100, Glencross, Christian wrote: > Can anyone provide a recommendation about how I should create a Maven > project which generates multiple JAR files from a single set of source > code? > > As some background, I had a "legacy" ANT build file with three build > targets: > 1. an RMI server implementation JAR, > 2. an RMI client implementation JAR, and > 3. a minimal client API JAR (i.e. includes only the public interfaces of > the client implementation, which other projects can compile against). > > I've migrated this across to Maven, but currently everything gets packaged > into a single JAR. It's not clear to me how I should structure my project to > reproduce how these 3 JARs were created by the original build process. > > I'd ideally solve this by creating 3 directories under 'src' (i.e. 'api', > 'client', 'server'), and then configuring multiple build targets for Maven > to use different source sets. The source set property seems to be > initialized from the POM. Are there hooks available to override this value > from my ANT files either before delegating to build-maven.xml, or in a > callback? Are there other alternatives? -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
