Yes, you should create two modules - one that produces a JAR, and one
that produces a WAR (and has a dependency on the module generating the
JAR).
It should be something like this:
root
|
+---pom.xml
|
+---war-module
| |
| +-----pom.xml
| |
| +-----src...
|
+---jar-module
|
+---pom.xml
|
+---src...
I'd recommend both modules' pom.xml inherit from the root pom.xml (it
should have packaging=pom). The 'war-module' - you may rename it to
'war' - should depend on the 'jar-module'.
If you need a full J2EE app, you can create another 'ear'
module...which depends on the 'war' module, and so forth.
On 10/14/05, Michael McCrann <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I am converting an Ant based project to M2.
>
> The project creates two artifacts: a war and a jar.
>
> My understanding is that an M2 project should only produce one artifact.
>
> So, what would the M2 approach be? multiple modules?
>
> Regards
>
> Michael McCrann
>
>
> NOTICE
> This e-mail and any attachments are confidential and may contain copyright
> material of Macquarie Bank or third parties. If you are not the intended
> recipient of this email you should not read, print, re-transmit, store or act
> in reliance on this e-mail or any attachments, and should destroy all copies
> of them. Macquarie Bank does not guarantee the integrity of any emails or any
> attached files. The views or opinions expressed are the author's own and may
> not reflect the views or opinions of Macquarie Bank.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
