>-----Original Message----- >From: Ron Wheeler [mailto:rwhee...@artifact-software.com] > > This is a bit on the edge of Tomcat and Maven but I am hoping that >there is a Maven solution or some little trick that makes the problem go >away. > >Our LMS portal consists of 60 separate modules that we build using >Maven. About 45 are webapps that we need to deploy to make a new >release. Another 10 or so are libraries that get deployed to the >sharable lib folder n Tomcat. > >When we build them with Maven, we get a nice xyz-1.9.1.war file but we >can't (or do not know how to) deploy it with the version number intact >and still have it run. Tomcat includes the version in the deployed >webapp which screws up names of things. > >The lib files don't care about names. > >We have solved this with an Ant script that strips off the version >number to give us xyz.war.
If you're using an ant script, you can use the tasks included with tomcat to deploy things with whatever name you want. Try looking at the instructions on this page: http://raibledesigns.com/wiki/Wiki.jsp?page=TomcatAntTasks (there are many others on the web too) If you don't need something quite so automated, you can also use the "deploy war file located on server" portion of the tomcat manager webapp, and specify whatever context path you need. However, if you're using maven's tomcat-maven-plugin, you might want to examine the "path" parameter on http://mojo.codehaus.org/tomcat-maven-plugin/deploy-mojo.html eric --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
