> Date: Sat, 12 Jan 2013 02:00:38 -0800 > From: [email protected] > To: [email protected] > Subject: Re: Deploy a project to multiple locations > > The thread shows different assumptions about " a project" because "deploying > a project" needs to be clearly defined. The output of your maven build could > be i.e. axis2.war, and that new version of axis2.war could be deployed to > severla application servers i.e. apache tomcats application directory, where > apache tomcat finds it and deploys it further inclusing activation of > axis2-1.62. > > OR > > it could mean, when the axis2-1.6.2 sources haven been built and tested > successfully on maven, then I would like to deploy the axis2-1.6.2 sources > to several servers and initiate a maven build process there.
Martin>so if i read between the lines i *think* you want to change the deployable characteristics Martin>as you deploy from one server to another Martin>you can achieve that objective by manipulating the MANIFEST.MF for the war Martin>and use maven-war-plugin to create custom MANIFEST.MF and then to build the war Martin>http://maven.apache.org/plugins/maven-war-plugin/manifest-mojo.html > OK - why should you do so? But just as an example, because I do not know > what you mean when you refere to "a project" or "to deploy a project". > > What is your project ? What is expected at the remote servers? > > Josef Martin>I agree with Josef there are way to many unknowns Martin>ask your client what axis2.war characteristics are expected at the remote servers Martin>*Viel Gluck* > > -- > View this message in context: > http://maven.40175.n5.nabble.com/Deploy-a-project-to-multiple-locations-tp5742898p5743087.html > Sent from the Maven - Users mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] >
