> -----Original Message----- > From: James Ward [mailto:[EMAIL PROTECTED] > Sent: 17 July 2003 21:50 > To: Maven Users List > Subject: RE: WAR file naming > > Actually if you are packaging your war into an ear, you can specify the > context, or if you have jboss you can put a jboss-web.xml in your > WEB-INF and specify it there. Regardless, the default behavior should > be the same as the jar and ejb plugins where it is named with the > version.
+1 > And of course there should be some way to override the name if > you do not want to specifically set the war's context using one of the > previously mentioned methods (or a different method). > > -James > > > On Thu, 2003-07-17 at 13:37, Michal Maczka wrote: > > > -----Original Message----- > > > From: Andy Jefferson [mailto:[EMAIL PROTECTED] > > > Sent: Thursday, July 17, 2003 9:01 PM > > > To: Maven Users List > > > Subject: WAR file naming > > > > > > > > > Its been raised as an issue by others but for a Maven newcomer, is > there > > > any reason why the WAR file has a naming that omits the version and > > > hence is inconsistent with the JAR and EAR namings. > > > > Yes. For many(all?) Servlet engines war file name = root context of the > web > > application. > > That's why many users prefer to have an artifact which is ready to > deploy. > > > > > In addition, it uses > > > the Ant task 'jar' instead of the Ant task 'war'. > > > > > > > Basically war task is simple extension of jar task: > > > > > http://cvs.apache.org/viewcvs/ant/src/main/org/apache/tools/ant/taskdefs /W > ar > > .java > > > > and really does nothing special but provides you some nested tags which > help > > you > > to put together files from different locations into war file. > > In maven this is already solved/configurable in different way > > and processing without using war task seems to be simpler > > (e.g. no warning is printed when WEB-INF folder contains web.xml file). > > > > > > Michal > > > > > > > > > > > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
