j2ee deploy with maven?

[Francisco Treacy <fr...@yahoo.fr>]

Hi there!

I'm new to Maven and I'm having some trouble with deployment-oriented tasks...

I recently discovered that Maven doesn't support J2EE-server deployment "out-of-the-box", and I'm trying to build up this part for our application. I have some questions cause I couldn't find the right answers on the web.

1. What do you suggest me to do in case of having a JBoss server and want to copy/deploy files to it? (Not only jars+wars but lots of xmls, too)
Conceptually, where does this task belong to? Should I extend the default lifecycle to be able to execute, e.g.: mvn -e jboss-deploy? What have you guys done?

2. Regarding these issues, we've created a new type of artifact that packages everything that should be deployed, although we ignore if it's the good way to do so. We would like to use Maven (through a plugin) to handle this special artifact by resolving* its path to the actual network/disk resource, and decompress it into our J2EE server folders.
(*) So there is our problem: what's the mechanism to resolve an artifact/dependency programmatically in our plugin?

 Thanks in advance for your replies,

Francisco

Re: j2ee deploy with maven?

[dan tran <da...@gmail.com>]

On 9/19/06, Francisco Treacy <fr...@yahoo.fr> wrote:
>
> Hi there!
>
> I'm new to Maven and I'm having some trouble with deployment-oriented
> tasks...
>
> I recently discovered that Maven doesn't support J2EE-server deployment
> "out-of-the-box", and I'm trying to build up this part for our application.
> I have some questions cause I couldn't find the right answers on the web.




1. What do you suggest me to do in case of having a JBoss server and want to
> copy/deploy files to it? (Not only jars+wars but lots of xmls, too)
> Conceptually, where does this task belong to? Should I extend the default
> lifecycle to be able to execute, e.g.: mvn -e jboss-deploy? What have you
> guys done?


 http://cargo.codehaus.org/Home
http://mojo.codehaus.org/jboss-maven-plugin/


2. Regarding these issues, we've created a new type of artifact that
> packages everything that should be deployed, although we ignore if it's the
> good way to do so. We would like to use Maven (through a plugin) to handle
> this special artifact by resolving* its path to the actual network/disk
> resource, and decompress it into our J2EE server folders.
> (*) So there is our problem: what's the mechanism to resolve an
> artifact/dependency programmatically in our plugin?


deploy your atifact to your internal repo, and have maven-denpendcy-plugin
to unpack it before calling jboss plugin to deploy files to your server.

Thanks in advance for your replies,
>
> Francisco
>
>
>

RE: j2ee deploy with maven?

[Scott Ryan <sc...@theryansplace.com>]

You can use the Cargo plugin in maven to ge the functionality that you need.
They support deployment to a number of containers.

Scott Ryan
Chief Technology Officer
Soaring Eagle L.L.C.
scott@theryansplace.com
www.soaringeagleco.com
(303) 263-3044

-----Original Message-----
From: Francisco Treacy [mailto:franciscotreacy@yahoo.fr]
Sent: Tuesday, September 19, 2006 5:49 AM
To: users@maven.apache.org
Subject: j2ee deploy with maven?


Hi there!

I'm new to Maven and I'm having some trouble with deployment-oriented
tasks...

I recently discovered that Maven doesn't support J2EE-server deployment
"out-of-the-box", and I'm trying to build up this part for our application.
I have some questions cause I couldn't find the right answers on the web.

1. What do you suggest me to do in case of having a JBoss server and want to
copy/deploy files to it? (Not only jars+wars but lots of xmls, too)
Conceptually, where does this task belong to? Should I extend the default
lifecycle to be able to execute, e.g.: mvn -e jboss-deploy? What have you
guys done?

2. Regarding these issues, we've created a new type of artifact that
packages everything that should be deployed, although we ignore if it's the
good way to do so. We would like to use Maven (through a plugin) to handle
this special artifact by resolving* its path to the actual network/disk
resource, and decompress it into our J2EE server folders.
(*) So there is our problem: what's the mechanism to resolve an
artifact/dependency programmatically in our plugin?

 Thanks in advance for your replies,

Francisco




---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org