<finalName> in your POM can be used to get a plainly-named version in the target directory.
The maven assembly plugin could be use to collect all the war files into a directory or tarball with their names changed following a pattern. the dependency plugin could be used to fetch them with their names changed. On Mon, Aug 23, 2010 at 2:42 PM, Ron Wheeler <rwhee...@artifact-software.com> wrote: > 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. > > What is the "Best Practice" solution to this. > > We still end up with a bunch of war files that are not deployed to Nexus > since Maven deploys the xyz-1.9.1.war file. > > > Ron > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
