> > 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. > > Can you do this with Tomact :P?
I've no idea what you can or can't do on Tomcat, but my experience of servlet engines is that you can configure the servlet context for any war passed in. PS. Tomcat can be used by JBoss, and JBoss manages to pass it into the correct servlet context on Tomcat :P > >Regardless, the default behavior should > > be the same as the jar and ejb plugins where it is named with the > > version. 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). > > > I see almost no reason why user would like to override war file name. > If you have good reasons for that rise an issue in JIRA. > (I myself believe that what is in POM is sufficient). > > I think that Maven should be as strict with war file naming as it is with > jars and do not let user override it. Can't agree with you on that one. Consistency is consistency - and Maven doesnt have it at present. Name the files in a consistent manner. If your servlet engine really doesn't allow you to cope with a versioned file then why not allow you the option of configuring the filename. -- Andy --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
