Wendy mentioned a "pull" model, and that's what we are doing. Ant with Maven tasks is great for this. Our Ant script itself is in Maven repository. We get that with a simple wget from a target server and then run the Ant script that gets all the other dependencies, installs the container, asks input for configuration items etc. As a bonus, we can automate testing of deployment this way.
Kalle On 11/6/07, Simon Taylor <[EMAIL PROTECTED]> wrote: > > Great thanks for that - will look at SCM tools > > -----Original Message----- > From: Wendy Smoak [mailto:[EMAIL PROTECTED] > Sent: 06 November 2007 03:33 > To: Maven Users List > Subject: Re: Deploy to production from a production Maven repository > > On 11/5/07, Simon Taylor <[EMAIL PROTECTED]> wrote: > > > I've recently seen the light of using Maven to build projects. > > A convert! :) > > > I understand that once complete artifacts are deployed to a > "production" > > Maven repository so they can be consumed as ready. > > Whats not clear to me is whether Maven is the tool to then consume > > that production ready artifact and deploy it to the producton server > > ready to be run up as a production app. > > Can someone clarify for me how they consume a Maven production > > artifact on their production server. > > You can take a look at the Cargo project or the various plugins that > deploy to appservers, but usually there is a configuration management > group in charge of deployment and you will have to follow their > procedures in order to get anything deployed into production. > > Where I am now we're looking at improving the automation of deployment, > but probably more in a "pull" model. The Maven repo has a nice standard > structure so it's easy to construct urls if you know the groupId, the > artifactId and the version number. So rather than try to have Maven > deploy things, it's more likely that we'll "notify" another system or > group of people, maybe provide a url, and have them pull what they need. > > -- > Wendy > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
