Re: j2ee vs ear, ejb, war

[Nathan Coast]

the j2ee plugin was split into the other plugins to promote more 
'component-based' development.  Last time I looked, the Appserver tasks 
were the only non-redundant goals in the j2ee plugin.  These might by 
now also have been moved elsewhere.

Srinivas Pavani wrote:

Hi,

Can anyone explain why the redundancy of plugins exists for creating ear, ejb and war modules? Should one use the j2ee plugin (which is missing the war generation goal) or should one stick with war, ejb, and ear plugins? Also, the properties for ejb and ear seem to overlap for maven.final.name?





---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]