Well, forget production. I would think the first question would be how to get Maven to keep deploying to a server, say JBoss.
This functionality is certainly needed and it's needed as part of a recompile/retest process. For example, if you have a web app and you just changed some servlets/jsp pages, you don't want to go through some other script to deploy. It would be ideal that Maven would just "do its magic" and deploy it to your local server, so you can quickly take a look if what you did fixed/update what you wanted. Invoking an Ant target (even if within Maven) is not really so great at all. One of the main point of Maven for me is the dependency handling. If I have to go back to Ant to deploy, I would, once again, have to pull out of a folder full of jars (the maven repository) the jars that I need for deployment. That's quite a job. So, the question still stands. I guess something like Cargo could do it. However, my co-workers have tried it and had tons of problems with it. Like a lot of things in Maven you gotta find that magic combination of plugin version numbers and work properly, so maybe that was what their problem was... I don't know. On 9/21/07, Wayne Fay <[EMAIL PROTECTED]> wrote: > Then you probably want to look at Cargo: > http://cargo.codehaus.org/JBoss+4.x > http://cargo.codehaus.org/Maven2+plugin > > They have mailing lists etc like Maven, so if you can't find what you > need or things aren't working as you expected, search the archives or > send an email to their user list. > > Wayne > > On 9/21/07, Dave Rathnow <[EMAIL PROTECTED]> wrote: > > > > We are building webapps and standalone apps. Our web container is > > Jboss. > > > > > > -----Original Message----- > > From: Wayne Fay [mailto:[EMAIL PROTECTED] > > Sent: September 21, 2007 10:00 AM > > To: Maven Users List > > Subject: Re: General question about how to use Maven to build and deploy > > > > Ant > > Cargo > > Various other container-specific plugins Manual copy etc > > > > We certainly do not automate deployment to Production. But it makes > > sense to set up a Continuous Integration server and perhaps automate > > deployment to a CI deployment environment. > > > > What kind of app are you building, Dave? And what container are you > > using? > > > > Wayne > > > > On 9/21/07, Farhan Sarwar <[EMAIL PROTECTED]> wrote: > > > Thats something i would be interested in knowing as well, as to what > > > people are using for automated deployment of their wars/ears or are > > > they still relying on some manual effort, i know of few using ant for > > > the same. > > > > > > Farhan. > > > > > > > > > to my knowledge most of the people are currently using or ant or other > > > > > scripts > > > > > > On 9/21/07, Dave Rathnow <[EMAIL PROTECTED]> wrote: > > > > So I've now got Maven to build my jars, wars, and ears, it installs > > > > them in my local repository and deploys to my remote repositories. > > > > But what do I do now? In order to run and test my apps, I have to > > > > manualy copy files to the appropriate directories, which seems a bit > > > > > > primative for such a complex tool as Maven. The next step I'll have > > > > > > to figure out is how to build an install kit with Maven, which may > > > > not be that hard since everything is in the respository. > > > > > > > > Still, I'm wondering how others are using Maven in their development > > > > > > process? Do you us Maven to build and deploy your files and then > > > > have another script copy them to directories for testing/kit > > building? > > > > > > > > Thanks, > > > > Dave. > > > > > > > > > > --------------------------------------------------------------------- > > > 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] > > > > > > --------------------------------------------------------------------- > > 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] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
