Hi Edgar, Yes, there is a good reason ! :-)
War is about building Wars, not Ear ... An Ear is a set of J2EE Modules : WAR, RAR, EJB-JAR + dependent libraries The idea (at least my vision :-)), is to have several plugins : - one War plugin (to create War modules) - one Ejb plugin (to create Ejb jars modules) - one Rar plugin (to create Rar modules) - one Ear plugin (to create a j2ee application) - one or several deploy plugins to deploy Ears to different application servers Hope it helps -Vincent > -----Original Message----- > From: Edgar Gonz�lez [mailto:[EMAIL PROTECTED]] > Sent: 19 August 2002 15:43 > To: [EMAIL PROTECTED] > Subject: Missing the EAR Goal > > Hi, > > Is there any reason to ommit an EAR goal in the war plugin? > > Edgar -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
