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?
Any hints, suggestions or references to examples in other Turbine projects
would be appreciated.
Thanks,
Chris
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
