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
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 j2ee plugin has no functionality in it for creating wars, ears and ejb
jars. It did originally, and it was split out into those three. All that
remains in j2ee is war-validate, which should be moved to the war plugin.
--
dIon Gillard, Multitask Consulting
Blog:
