Indeed. Sorry I read the topic too quickly to give a wrong answer ;-)
Leon, why do you explicitly need to install the war file in your m2repo with a custom name? Couldn't you simply use the one you can find in the target/ folder? Or you can always use the maven-resources-plugin to copy the generated war to a given specific folder. Cheers, Reynald On Wednesday, January 5, 2011 at 19:30 , Haszlakiewicz, Eric wrote: > > > -----Original Message----- > > From: Reynald Borer [mailto:reynald.bo...@gmail.com] > > > > You can modify the finalName tag to change the name of artifact. By default > > it is defined like the following: > > <project> > > <build> > > <finalName>${artifactId}-${version}</finalName> > > </build> > > </project> > > > > > > That only affects what gets created in your "target" directory. Once the > artifact gets uploaded to a repository (e.g. ~/.m2, or a central Nexus repo) > the "standard" naming is enforced. > > The finalName tag is really only useful if you skip the deploy step and use > the output artifact directly. (e.g. as part of a larger, non-maven build, or > emailing it to a customer, etc...) > > eric > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > > > >
