The same way you publish a released artifact: mvn deploy. You do need a corporate Maven repo setup. And your CI server needs to have a settings.xml file which know were it is so Maven can deploy to it.
--- Todd Thiessen > -----Original Message----- > From: Neil Chaudhuri [mailto:nchaudh...@potomacfusion.com] > Sent: Wednesday, November 11, 2009 12:16 PM > To: Maven Users List > Subject: RE: Automated Build and Check In > > I am in fact using a CI tool. So I can build a WAR at regular > intervals. But publishing the SNAPSHOT, how do you do that? > > Thanks. > > > -----Original Message----- > From: Nayan Hajratwala [mailto:na...@chikli.com] > Sent: Wed 11/11/2009 10:49 AM > To: Maven Users List > Subject: Re: Automated Build and Check In > > Sounds like you could benefit from a Continuous Integration > Server ... Try https://hudson.dev.java.net/ -- very easy to set up. > > You could configure it to check in the generated artifact via > a post-build command (setup via hudson), but you might want > to consider just publishing your generated WAR SNAPSHOT > version to an internal maven repo (i.e. Nexus). Hudson can do > this for you as well. > > > On Nov 11, 2009, at 11:39 AM, Neil Chaudhuri wrote: > > > I would like to do something very simple at regular > intervals (say every hour): > > > > *Build the primary artifact-- a WAR file *Check it into SVN at a > > specified location in the trunk > > > > How could I do this? > > > > Thanks. > > > > > --------------------------------------------------------------------- > 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
