> -----Original Message----- > From: James Ward [mailto:[EMAIL PROTECTED] > Sent: Thursday, July 17, 2003 9:50 PM > 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.
Can you do this with Tomact :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. Note that when war is deployed/installed to repository the war file name _always_ contains the version. IMHO communication between project and artifact exchange via local repository is better practice, then digging in folders of some other projects. So if you use repository you have versioned artifacts. So e.g. when you are building your ear - and you want to use some war created by other subproject, you should take this artifact from repository. And you do this by putting appropriate dependency into your POM. Michal --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
