Understood. So you want your users to download the WAR directly from either your m2repo (weird) or from a Maven repository tool like Nexus, right?
In that case, I don't think it's a Maven problem. You should consider deploying your generated war file to a web server like Apache (through maven-resources-plugin for example). Or you might also have an Apache in front of your Nexus server that is correctly configured to rewrite "/xyz/distributeme.war" to the correct location of the latest war in Nexus, and then it'll be downloaded as distributeme.war. Regards, Reynald On Wednesday, January 5, 2011 at 21:00 , Leon Rosenberg wrote: > Hello Reynald, > > I posted it in my original post. > The webapp have to be accessed by a specific context-path, e.g. > http://host:port/distributeme/registry/list > > The easiest way to achieve it, is to name the war distributeme.war. > > In other words, for external users its easier to understand: > "Download distributeme.war from xyz and place it under webapps in your > app container " > as > "Download version-x from xyz, rename it to distributeme.war and than > place it under webapps in your app container" > > regards > Leon > > > On Wed, Jan 5, 2011 at 7:52 PM, Reynald Borer <reynald.bo...@gmail.com> wrote: > > > 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 > > > > > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > > > >
