Ok, I was mixing things up in my response below. Please ignore it!

However, Cargo does support non-exploded deployment of an artifact from a
maven repo (through its maven plugin). That's explained here:
http://cargo.codehaus.org/Deploying+to+a+running+container

/Anders

On Thu, Aug 12, 2010 at 06:39, Anders Hammar <[email protected]> wrote:

> You could take a look at the Codehaus Cargo project. It's a generic
> container API and it's maven plugin supports deployment to a container from
> an URL. I'm not sure about exploded though, please check!
>
> /Anders
>
> On Wed, Aug 11, 2010 at 21:41, Nestor Urquiza <[email protected]>wrote:
>
>> Just in case this help here is a post (
>> http://thinkinginsoftware.blogspot.com/2010/08/release-and-deploy-using-maven-svn.html)
>>  about what I am doing using bash. I would love to have all the features
>> explained there implemented as part of the Tomcat Maven Plugin (snapshot
>> from svn, exploded deployment, release from artifactory, front end
>> deployment or webapps from svn)
>>
>>
>> On Wed, Aug 11, 2010 at 12:11 PM, Nestor Urquiza <
>> [email protected]> wrote:
>>
>>> Hello guys,
>>>
>>> I have been using for more than two years my own Perl + maven + ant
>>> scripts to deploy to jboss from both SVN trunks and released artifactories
>>> in Archiva.
>>>
>>> Now that I am using tomcat more and more I wanted to know if there are
>>> any plans or perhaps options that I cannot see from
>>> http://mojo.codehaus.org/tomcat-maven-plugin/ that will allow me to:
>>>
>>> 1. Deploy a war artifact directly from a repository URL for example
>>> Artifactory.
>>> 2. Deploy a war file directly from a project svn URL.
>>>
>>> In both cases it should be supported exploded deployment.
>>> In both cases it should be supported to deploy *only* webapps folder in
>>> an exploded deployment. I have done this with rsync in the past and it is a
>>> must have when you want the Designers to push static images, css, js and so
>>> on directly from an SVN URL.
>>>
>>> Thanks!
>>>
>>> -Nestor Urquiza
>>>
>>>
>>
>

Reply via email to