Nabble - Cargo - User

Re: Setting up

2009-11-12T03:39:26Z

Hi all,

Just so this answer is recorded somewhere (I certainly couldn't find a decent example anywhere on the web) this worked for me:

To use cargo-maven2-plugin to deploy to a remote server but use a settings.xml file for the username and password you can use a profile with properties and use those properties but probably easier:

define a server in your settings.xml file for example like this:

<container>
<containerId>tomcat6x</containerId>
<type>remote</type>
</container>


<configuration>
<type>runtime</type>
<properties>
<cargo.server.settings>myServer</cargo.server.settings> 
</properties>
/configuration>

then define a server in your ~/.m2/settings.xml file

<id>myServer</id>

<cargo.tomcat.manager.url>http://myexampleurl.com/manager</cargo.tomcat.manager.url>

<cargo.remote.username>foo</cargo.remote.username>

<cargo.remote.password>bar</cargo.remote.password>

</configuration>

</server>

</servers>

</settings>

and you should be away

On 12 Nov 2009, at 11:24, Alexander Brill wrote:

On Wed, Nov 11, 2009 at 3:35 PM, Robert Denison <rob@...> wrote:
Hi,

I'm using cargo-maven2-plugin to deploy to my running tomcat container. While testing I have my connect details (username password etc) in my pom.xml.

Now I'm ready to go live I want to remove them. Searching seems to yield 3 possibilities using settings.xml - using profiles and properties, or standard maven2 <server> tags, or I found this reference to different server tags http://jira.codehaus.org/browse/CARGO-596 involving elements like cargo.remote.password.

Can anyone tell me what the correct method for keeping login details out of your pom is when using this plugin? If this is documented somewhere I would love a link as I've spent quite a bit of time searching for this answer. Failing that if someone has the time a small example of what you would use would be perfect.

Thanks for any help.

R.

You could put your login details in .m2/settings.xml.
Something like this:

<properties>
<tomcat.server.1.username>myuser</tomcat.server.1.username>

<tomcat.server.1.passwd>password</tomcat.server.1.password>
</properties>

And then reference them in your pom.xml as a variable with ${tomcat.server.1.username}

Alexander
http://brill.no

Re: Setting up

2009-11-12T03:24:54Z

On Wed, Nov 11, 2009 at 3:35 PM, Robert Denison <rob@...> wrote:

Hi,

I'm using cargo-maven2-plugin to deploy to my running tomcat container. While testing I have my connect details (username password etc) in my pom.xml.

Now I'm ready to go live I want to remove them. Searching seems to yield 3 possibilities using settings.xml - using profiles and properties, or standard maven2 <server> tags, or I found this reference to different server tags http://jira.codehaus.org/browse/CARGO-596 involving elements like cargo.remote.password.

Can anyone tell me what the correct method for keeping login details out of your pom is when using this plugin? If this is documented somewhere I would love a link as I've spent quite a bit of time searching for this answer. Failing that if someone has the time a small example of what you would use would be perfect.

Thanks for any help.

R.

You could put your login details in .m2/settings.xml.

Something like this:

<tomcat.server.1.username>myuser</tomcat.server.1.username>

<tomcat.server.1.passwd>password</tomcat.server.1.password>

</properties>

And then reference them in your pom.xml as a variable with ${tomcat.server.1.username}

Alexander

http://brill.no

Setting up

2009-11-11T05:35:55Z

Hi,

I'm using cargo-maven2-plugin to deploy to my running tomcat container. While testing I have my connect details (username password etc) in my pom.xml.

Now I'm ready to go live I want to remove them. Searching seems to yield 3 possibilities using settings.xml - using profiles and properties, or standard maven2 <server> tags, or I found this reference to different server tags http://jira.codehaus.org/browse/CARGO-596 involving elements like cargo.remote.password.

Can anyone tell me what the correct method for keeping login details out of your pom is when using this plugin? If this is documented somewhere I would love a link as I've spent quite a bit of time searching for this answer. Failing that if someone has the time a small example of what you would use would be perfect.

Thanks for any help.

R.

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

Re: CARGO 1.0.1

2009-11-10T00:59:06Z

Hello again

S. Ali Tokmen a écrit :
> CARGO 1.0.1-alpha-1 is working fine with JOnAS 5.1.0 final (we use it
> in multiple Maven projects for integration testing of our Java EE and
> OSGi applications). You'd have at least my "go" :)

It actually doesn't, see http://jira.ow2.org/browse/JONAS-64

It works only with CARGO 1.0.1-SNAPSHOT now. I'd definitely say "yes" to
a CARGO 1.0.1 or 1.0.1-alpha-2

Cheers

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

Odp:jetty6x/embedded ClassNotFoundException: HttpServlet

2009-11-09T04:59:34Z

Hi all,

I have just confirmed that Apache ODE works on an embedded Jetty using maven-jetty-plugin. It integrates smoothly with my failsafe integration tests.

But I'd like to use a more generic Cargo approach... I'm still interested in learning how the HttpServlet ClassNotFound exception can be dealt with.

thanks,
Łukasz

W dniu 09-11-2009 12:25 lukasz.budnik@... napisał(a):

> Hi all,
>
> While deploying external war (deployables/deployable) I keep getting:
>
> Caused by: java.lang.ClassNotFoundException: javax.servlet.http.HttpServlet
>
> Has anyone experienced it before? If so and have found solution please share some tips.
>
> If anyone hasn't encounter this error, below is "my story".
>
> I have integration test which involves communicating with Apache ODE (WS-BPEL engine, based on Axis2).
> Till now when I had to invoke integration tests I had to make sure if external Tomcat with Apache ODE is up and running.
> Using cargo I wanted to automate this process by running Apache ODE on an embedded Jetty 6 container.
> And this is where I have the problem. During the deployment of Apache ODE on embedded Jetty6 I have class not found exception.
>
> When I deploy Apache ODE on local Jetty 6.1.21, it deploys successfully.
>
> Any ideas what may be causing this exception?
>
> thanks
> Łukasz

jetty6x/embedded ClassNotFoundException: HttpServlet

2009-11-09T03:25:14Z

Hi all,

While deploying external war (deployables/deployable) I keep getting:

Caused by: java.lang.ClassNotFoundException: javax.servlet.http.HttpServlet

Has anyone experienced it before? If so and have found solution please share some tips.

If anyone hasn't encounter this error, below is "my story".

I have integration test which involves communicating with Apache ODE (WS-BPEL engine, based on Axis2).
Till now when I had to invoke integration tests I had to make sure if external Tomcat with Apache ODE is up and running.
Using cargo I wanted to automate this process by running Apache ODE on an embedded Jetty 6 container.
And this is where I have the problem. During the deployment of Apache ODE on embedded Jetty6 I have class not found exception.

When I deploy Apache ODE on local Jetty 6.1.21, it deploys successfully.

Any ideas what may be causing this exception?

thanks
Łukasz

Re: WebLogic 10.x automatic installation

2009-11-04T05:52:56Z

Hi Adrian,

As far as I understood from your previous reply I have to install weblogic manually, but cargo will create weblogic domain automatically, run it and deploy application.

I am using ant to run weblogic 10.3, but it does not work. I tried to find working example on the web but I failed.

Do you have documentation or samples for weblogic (ant extension) ?

Thank you in advance,
Petr

On Tue, Aug 25, 2009 at 9:33 PM, Adrian Cole <ferncam1@...> wrote:

Hi, Petr.

Cargo creates single-server weblogic domains when given an existing
weblogic home. Cargo does not do auto-installation of weblogic
binaries.

I recommend installing the weblogic home once and then setup some
system for distributing it where needed. Once the binaries are
present, cargo can install domains.

I hope this helps,
-Adrian

On Tue, Aug 25, 2009 at 8:40 AM, Peter
Pleshachkov<peter.pleshachkov@...> wrote:
> Dear Cargo developers,
>
> I am going to use your project to automate WebLogic 10.0 Application Server
> management like install, start, stop, etc. In your documentation you say
> that automatic installation of WebLogic 10.x (Installer feature) is
> supported. However, you support automatic installation only for zip
> archives. But WebLogic App mServer is distributed as .exe file under Windows
> which you should manually to run and follow the installation dialogs. So the
> question is : Do you support automatic installation of WebLogic 10.x ? If
> yes how do you achieve that ?
>
> Thank you in advance,
> Petr Pleashachkov

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

Cargo maven2 plugin: deployment on 2 container instances with different configuration

2009-10-31T19:43:20Z

Hi,

I am trying to deploy a deployable on 2 instances of an InstalledLocalContainer using different configurations.
To achieve this I use a maven configuration similar to this one: http://old.nabble.com/Multiple-Tomcat-Containers-and-Not-Automatically-deploying-Maven-2-project-artifact-ts7631458.html#a7631458.
My configuration defines 2 executions (different ids) calling cargo goal 'start' with different parameters for underlying StandaloneLocalConfiguration.
It looks like from my tests that the configuration of second execution is ignored (non-existent class for implementation node doesn't generate errors).

As the InstalledLocalContainer I am using is a custom implementation (no plugin available for this container) I am wondering if this kind of scenario is supported or if the implementation is wrong.
Could someone confirm if this use case is supported by cargo?

Thanks,
Julien

Settting root context in Weblogic

2009-10-19T10:26:16Z

Hi all,

My application is packaged as myapplication.war, but when deployed in Weblogic I want to use 'app' as the root context. I added 'context' property under deployable element which works in Tomcat, but not in WL. So how do you configure it in WL ?

Thanks & Regards,

Setya

Re: Cargo is unable to find Weblogic home

2009-10-19T10:15:52Z

Hi,

Thanks for your advice.

I just changed the path into '/home/setya/Programs/wls103/wlserver_10.3' and it worked.

Regards,

Setya

Re: Cargo is unable to find Weblogic home

2009-10-19T08:55:55Z

Sorry you are having problems.

In weblogic land, there are 2 homes: BEA_HOME and WL_HOME.

By default, WL_HOME is the path of weblogic10.3/ and BEA_HOME is the
path including WL_HOME and also (very importantly) modules.

To reset the BEA_HOME, use the property cargo.weblogic.bea.home.

I hope this helps.

Cheers,
-Adrian

On Mon, Oct 19, 2009 at 7:25 AM, Setya <jsetya@...> wrote:

>
> Hi all,
>
> I specify '/home/setya/Programs/wls103' as Weblogic home, but Cargo keeps
> throwing the following exception :
>
> org.codehaus.cargo.container.ContainerException: Invalid Weblogic
> installation. The [/home/setya/Programs/modules] directory doesn't exist.
> Make sure the BEA_HOME directory you have specified points to the right
> location (It's currently pointing to [/home/setya/Programs])
>
> It seems I encounter bug http://jira.codehaus.org/browse/CARGO-691
> http://jira.codehaus.org/browse/CARGO-691
>
> Any workaround, anyone ?
>
> Any help would be greatly appreciated.
>
> Regards,
>
> Setya
> --
> View this message in context: http://www.nabble.com/Cargo-is-unable-to-find-Weblogic-home-tp25959243p25959243.html
> Sent from the Cargo - User mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
> http://xircles.codehaus.org/manage_email
>
>
>

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

Cargo is unable to find Weblogic home

2009-10-19T07:25:22Z

Hi all,

I specify '/home/setya/Programs/wls103' as Weblogic home, but Cargo keeps throwing the following exception :

org.codehaus.cargo.container.ContainerException: Invalid Weblogic installation. The [/home/setya/Programs/modules] directory doesn't exist. Make sure the BEA_HOME directory you have specified points to the right location (It's currently pointing to [/home/setya/Programs])

It seems I encounter bug http://jira.codehaus.org/browse/CARGO-691

Any workaround, anyone ?

Any help would be greatly appreciated.

Regards,

Setya

Re: CARGO 1.0.1

2009-10-02T03:02:37Z

Hi

Can you fix CARGO-705 (http://jira.codehaus.org/browse/CARGO-705) before
the release?
This is trivial one.

Grzegorz Slowikowski

S. Ali Tokmen wrote:
> Hello
>
> Any plans for a CARGO 1.0.1 release?
>
> Cheers
>

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

[M2 cargo plugin] org.codehaus.cargo.container.ContainerException: Failed to deploy

2009-10-01T01:46:14Z

Hi there,

I try to deploy my webapp to a remote tomcat 5x using maven cargo plugin.
The stacktrace I get is pasted att the bottom of the message, under my pom file.
Basically, the error I get seems to be coming from the tomcat manager itself, not cargo. It looks like cargo is telling tomcat to deploy in the root path ('/'). Indeed, I managed to get the webapp deployed in the root directory of tomcat webapps once. Well anyway, I don't want it in the root context, but in the xxxxxxx context.
Looks like the porperty 'context' of my pom file isn't transfered to tomcat. Is there anything wrong in my pom ?

Thank you,

Mathieu.

============= POM file ====================
<plugin>
<groupId>org.codehaus.cargo</

groupId>
                <artifactId>cargo-maven2-plugin</artifactId>
                <version>1.0</version>
                <configuration>
                    <wait>false</wait>
                    <container>
                        <containerId>tomcat5x</containerId>
                        <type>remote</type>
                        <append>true</append>
                    </container>
                    <configuration>
                        <type>runtime</type>
                        <properties>
                            <cargo.hostname>192.168.10.249</cargo.hostname>
                            <cargo.remote.username>XXXX</cargo.remote.username>
                            <cargo.remote.password>XXXX</cargo.remote.password>
                            <cargo.logging>high</cargo.logging>
                            <cargo.servlet.port>9090</cargo.servlet.port>
                            <cargo.tomcat.manager.url>http://192.168.10.249:9090/manager</cargo.tomcat.manager.url>
                        </properties>
                    </configuration>
                    <deployer>
                        <deployables>
                            <deployable>
                                <groupId>${project.groupId}</groupId>
                                <artifactId>xxxxxxx</artifactId>
                                <type>war</type>
                                <pingURL>http://192.168.10.249:9090/xxxxxxx</pingURL>
                                <pingTimeout>300000</pingTimeout>
                                <properties>
                                    <context>xxxxxxx</context>
                                </properties>
                            </deployable>
                        </deployables>
                    </deployer>
                </configuration>
                <executions>
                    <execution>
                        <id>deploy</id>
                        <phase>pre-integration-test</phase>
                        <goals>
                            <goal>redeploy</goal>
                        </goals>
                        <configuration>
                            <deployer>
                                <deployables>
                                    <deployable>
                                        <groupId>${project.groupId}</groupId>
                                        <artifactId>xxxxxxx</artifactId>
                                        <type>war</type>
                                        <pingURL>http://192.168.10.249:9090/xxxxxxx</pingURL>
                                        <pingTimeout>300000</pingTimeout>
                                        <properties>
                                            <context>xxxxxxx</context>
                                        </properties>
                                    </deployable>
                                </deployables>
                            </deployer>
                        </configuration>
                    </execution>
                    <execution>
                        <id>undeploy</id>
                        <phase>post-integration-test</phase>
                        <goals>
                            <goal>undeploy</goal>
                        </goals>
                    </execution>
                </executions>
            </plugin>

============= Maven trace =================
mhicauber@cdsi-wps:~/java/workspaces/workspace/cofParent/tests_fonctionnels$ mvn clean integration-test
[INFO] Scanning for projects...
[INFO] ------------------------------------------------------------------------
[INFO] Building testsSelenium
[INFO]    task-segment: [clean, integration-test]
[INFO] ------------------------------------------------------------------------
[INFO] [clean:clean]
[INFO] Deleting directory /home/mhicauber/java/workspaces/workspace/cofParent/tests_fonctionnels/target
[INFO] [compiler:testCompile {execution: default}]
[INFO] Compiling 2 source files to /home/mhicauber/java/workspaces/workspace/cofParent/tests_fonctionnels/target/test-classes
[INFO] [site:attach-descriptor]
[INFO] [cargo:redeploy {execution: deploy}]
[INFO] [mcat5xRemoteDeployer] Redeploying [/home/mhicauber/java/apache-maven-2.1.0/repository/com/sqli/xxxxxxx/xxxxxxx/1.0.1-SNAPSHOT/xxxxxxx-1.0.1-SNAPSHOT.war]
[INFO] [mcat5xRemoteDeployer] Undeploying [/home/mhicauber/java/apache-maven-2.1.0/repository/com/sqli/xxxxxxx/xxxxxxx/1.0.1-SNAPSHOT/xxxxxxx-1.0.1-SNAPSHOT.war]
[INFO] [mcat5xRemoteDeployer] Deploying [/home/mhicauber/java/apache-maven-2.1.0/repository/com/sqli/xxxxxxx/xxxxxxx/1.0.1-SNAPSHOT/xxxxxxx-1.0.1-SNAPSHOT.war]
[INFO] ------------------------------------------------------------------------
[ERROR] FATAL ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Failed to deploy [/home/mhicauber/java/apache-maven-2.1.0/repository/com/sqli/xxxxxxx/xxxxxxx/1.0.1-SNAPSHOT/xxxxxxx-1.0.1-SNAPSHOT.war]
ECHEC - l'application existe déjà dans le chemin /

[INFO] ------------------------------------------------------------------------
[INFO] Trace
org.codehaus.cargo.container.ContainerException: Failed to deploy [/home/mhicauber/java/apache-maven-2.1.0/repository/com/sqli/xxxxxxx/xxxxxxx/1.0.1-SNAPSHOT/xxxxxxx-1.0.1-SNAPSHOT.war]
    at org.codehaus.cargo.container.tomcat.internal.AbstractTomcatManagerDeployer.deploy(AbstractTomcatManagerDeployer.java:105)
    at org.codehaus.cargo.container.tomcat.internal.AbstractTomcatManagerDeployer.redeploy(AbstractTomcatManagerDeployer.java:179)
    at org.codehaus.cargo.maven2.DeployerRedeployMojo.performDeployerActionOnSingleDeployable(DeployerRedeployMojo.java:39)
    at org.codehaus.cargo.maven2.AbstractDeployerMojo.performDeployerActionOnAllDeployables(AbstractDeployerMojo.java:104)
    at org.codehaus.cargo.maven2.AbstractDeployerMojo.doExecute(AbstractDeployerMojo.java:47)
    at org.codehaus.cargo.maven2.AbstractCargoMojo.execute(AbstractCargoMojo.java:255)
    at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451)
    at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558)
    at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:499)
    at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:478)
    at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330)
    at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291)
    at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)
    at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
    at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
    at org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
    at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
    at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
    at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: org.codehaus.cargo.container.tomcat.internal.TomcatManagerException: ECHEC - l'application existe déjà dans le chemin /

    at org.codehaus.cargo.container.tomcat.internal.TomcatManager.invoke(TomcatManager.java:525)
    at org.codehaus.cargo.container.tomcat.internal.TomcatManager.deployImpl(TomcatManager.java:565)
    at org.codehaus.cargo.container.tomcat.internal.TomcatManager.deploy(TomcatManager.java:273)
    at org.codehaus.cargo.container.tomcat.internal.TomcatManager.deploy(TomcatManager.java:256)
    at org.codehaus.cargo.container.tomcat.internal.TomcatManager.deploy(TomcatManager.java:240)
    at org.codehaus.cargo.container.tomcat.internal.AbstractTomcatManagerDeployer.deploy(AbstractTomcatManagerDeployer.java:101)
    ... 23 more
org.codehaus.cargo.container.tomcat.internal.TomcatManagerException: ECHEC - l'application existe déjà dans le chemin /

    at org.codehaus.cargo.container.tomcat.internal.TomcatManager.invoke(TomcatManager.java:525)
    at org.codehaus.cargo.container.tomcat.internal.TomcatManager.deployImpl(TomcatManager.java:565)
    at org.codehaus.cargo.container.tomcat.internal.TomcatManager.deploy(TomcatManager.java:273)
    at org.codehaus.cargo.container.tomcat.internal.TomcatManager.deploy(TomcatManager.java:256)
    at org.codehaus.cargo.container.tomcat.internal.TomcatManager.deploy(TomcatManager.java:240)
    at org.codehaus.cargo.container.tomcat.internal.AbstractTomcatManagerDeployer.deploy(AbstractTomcatManagerDeployer.java:101)
    at org.codehaus.cargo.container.tomcat.internal.AbstractTomcatManagerDeployer.redeploy(AbstractTomcatManagerDeployer.ja

Re: JOnAS link missing

2009-09-30T05:47:53Z

Hello

Done :) I've managed to add Geronimo, Glassfish and JRun

Cheers

S. Ali Tokmen
savas-ali.tokmen@...

Office: +33 4 76 29 76 19
GSM: +33 66 43 00 555

Bull, Architect of an Open World TM
http://www.bull.com

Matt Wringe a écrit :
> you have to link your confluence account with your xircles account (its
> done through the xircles site)

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

Re: CARGO 1.0.1

2009-09-30T05:31:28Z

Hello

Matt Wringe a écrit :
> yeah, we should have another release soon. What do people think about 2
> weeks from now?
>

CARGO 1.0.1-alpha-1 is working fine with JOnAS 5.1.0 final (we use it in
multiple Maven projects for integration testing of our Java EE and OSGi
applications). You'd have at least my "go" :)

Cheers

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

Deploy exploded war

2009-09-30T03:46:19Z

Hi,

Is ti posible to deploy an exploded web archive to jboss server by cargo maven plugin?

Thansk

Best regards

Zlatko Josic

Re: JOnAS link missing

2009-09-29T10:26:30Z

On Thu, 2009-09-24 at 09:28 +0200, S. Ali Tokmen wrote:
> Hello
>
> I'm getting close! Foudn the button, created a confluence account, and
> now it says: "You cannot view this page due to inherited restrictions".
>
> Can you please fix this? My login is alitokmen.
you have to link your confluence account with your xircles account (its
done through the xircles site)

>
> Cheers
>
> S. Ali Tokmen
> savas-ali.tokmen@...
>
> Office: +33 4 76 29 76 19
> GSM: +33 66 43 00 555
>
> Bull, Architect of an Open World TM
> http://www.bull.com
>
>
>
> Matt Wringe a écrit :
> > On Mon, 2009-09-21 at 16:35 +0200, S. Ali Tokmen wrote:
> >
> >> Hello
> >>
> >> Matt Wringe a écrit :
> >>
> >>> JOnAS link added
> >>>
> >>>
> >> Thanks :)
> >>
> >>
> >>> Please note that it is a wiki and fixes like this are encouraged.
> >>>
> >>>
> >> You're absolutely right... And how do I log in to the wiki to edit the
> >> page, I didn't see the link? I would gladly add the links for Geronimo,
> >> Glassfish and jrun (which are also missing).
> >>
> >
> > there is an edit button on the bottom of each page
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
> http://xircles.codehaus.org/manage_email
>
>

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

Re: CARGO 1.0.1

2009-09-29T10:25:47Z

On Tue, 2009-09-29 at 14:12 +0200, S. Ali Tokmen wrote:

> Hello
>
> A version 1.0.1-alpha1 seems to be out... :)
>
> Cheers
>
> S. Ali Tokmen
> savas-ali.tokmen@...
>
> Office: +33 4 76 29 76 19
> GSM: +33 66 43 00 555
>
> Bull, Architect of an Open World TM
> http://www.bull.com
>
>
>
> S. Ali Tokmen a écrit :
> > Hello
> >
> > Any plans for a CARGO 1.0.1 release?

yeah, we should have another release soon. What do people think about 2
weeks from now?

> > Cheers
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
> http://xircles.codehaus.org/manage_email
>
>

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

Re: CARGO 1.0.1

2009-09-29T05:12:14Z

Hello

A version 1.0.1-alpha1 seems to be out... :)

Cheers

S. Ali Tokmen
savas-ali.tokmen@...

Office: +33 4 76 29 76 19
GSM: +33 66 43 00 555

Bull, Architect of an Open World TM
http://www.bull.com

S. Ali Tokmen a écrit :
> Hello
>
> Any plans for a CARGO 1.0.1 release?
>
> Cheers
>

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

Re: JOnAS link missing

2009-09-24T00:28:15Z

Hello

I'm getting close! Foudn the button, created a confluence account, and
now it says: "You cannot view this page due to inherited restrictions".

Can you please fix this? My login is alitokmen.

Cheers

S. Ali Tokmen
savas-ali.tokmen@...

Office: +33 4 76 29 76 19
GSM: +33 66 43 00 555

Bull, Architect of an Open World TM
http://www.bull.com

Matt Wringe a écrit :

> On Mon, 2009-09-21 at 16:35 +0200, S. Ali Tokmen wrote:
>
>> Hello
>>
>> Matt Wringe a écrit :
>>
>>> JOnAS link added
>>>
>>>
>> Thanks :)
>>
>>
>>> Please note that it is a wiki and fixes like this are encouraged.
>>>
>>>
>> You're absolutely right... And how do I log in to the wiki to edit the
>> page, I didn't see the link? I would gladly add the links for Geronimo,
>> Glassfish and jrun (which are also missing).
>>
>
> there is an edit button on the bottom of each page

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

Re: JOnAS link missing

2009-09-23T07:04:23Z

On Mon, 2009-09-21 at 16:35 +0200, S. Ali Tokmen wrote:

> Hello
>
> Matt Wringe a écrit :
> > JOnAS link added
> >
>
> Thanks :)
>
> > Please note that it is a wiki and fixes like this are encouraged.
> >
>
> You're absolutely right... And how do I log in to the wiki to edit the
> page, I didn't see the link? I would gladly add the links for Geronimo,
> Glassfish and jrun (which are also missing).

there is an edit button on the bottom of each page

> Cheers
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
> http://xircles.codehaus.org/manage_email
>
>

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

Re: Problem on a multi-modules project

2009-09-22T19:16:43Z

One workaround I have found is to attach the cargo mojo to a phase e.g. package or deploy in your cargo plugin section. so when you do mvn deploy or package from parent, it seems to work without any errors.

You may also try to add cargo plugin in the parent as well either in the pluginmanagement or standalone. It might work.

niaouli wrote:

Hello,

I am using Cargo on a multi-module project.
Everything is perfect when I work on the module project : mvn clean install cargo:deployer-redeploy

But when I did the same in the parent project, I got an error : The plugin 'org.apache.maven.plugins:maven-cargo-plugin' does not exist or no valid version could be found
So I changed the line for : mvn clean install org.codehaus.cargo:cargo-maven2-plugin:deployer-redeploy
Then I got another problem : For all packaging other than war you need to configure the container you wishes to use.

I would like to be able to work directly from the parent module, in order to enable Hudson (my continuous integration engine) to deploy automatically this web application. You can see below my pom.xml files, for the parent and then the concerned module.

Thanks for your help. Regards,

Mickaël T.

---------------------

<project>
<modelVersion>4.0.0</modelVersion>
<groupId>nc.ird</groupId>
<artifactId>MyProject</artifactId>
<packaging>pom</packaging>
<name>MyProject</name>
<version>0.1-SNAPSHOT</version>
<modules>
<module>MyProject.domain</module>
<module>MyProject.service</module>
<module>MyProject.web</module>
</modules>

</project>

---------------------

<project>
<parent>
<artifactId>MyProject</artifactId>
<groupId>nc.ird</groupId>
<version>0.1-SNAPSHOT</version>
</parent>
<modelVersion>4.0.0</modelVersion>
<groupId>nc.ird</groupId>
<artifactId>MyProject.web</artifactId>
<packaging>war</packaging>
<name>MyProject.web</name>
<version>0.1-SNAPSHOT</version>
<properties>
<deploy.host>deployHost</deploy.host>
<deploy.port>8080</deploy.port>
<deploy.user>deployUser</deploy.user>
<deploy.password>deployPassword</deploy.password>
</properties>
<build>
<plugins>
<plugin>
<groupId>org.codehaus.cargo</groupId>
<artifactId>cargo-maven2-plugin</artifactId>
<configuration>
<container>
<containerId>tomcat6x</containerId>
<type>remote</type>
</container>
<configuration>
<type>runtime</type>
<properties>
<cargo.tomcat.manager.url>http://${deploy.host}:${deploy.port}/manager/</cargo.tomcat.manager.url>
<cargo.remote.username>${deploy.user}</cargo.remote.username>
<cargo.remote.password>${deploy.password}</cargo.remote.password>
</properties>
</configuration>
<deployer>
<type>remote</type>
<deployables>
<deployable>
<groupId>${project.groupId}</groupId>
<artifactId>${project.artifactId}</artifactId>
<type>war</type>
<pingURL>http://${deploy.host}:${deploy.port}/${parent.project.build.finalName}/</pingURL>
</deployable>
</deployables>
</deployer>
</configuration>
</plugin>
</plugins>
</build>

</project>

Tomcat 6 + JAva API + Exploded WAR = Skips Deployment

2009-09-21T17:11:16Z

I'm using the Cargo Java API as part of a little functional testing framework and while it's working fantastic with WAR files it's not deploying exploded WARs.

Here's the relevant Cargo code:

// (1) Optional step to install the container from a URL pointing to its distribution

Installer installer = new ZipURLInstaller(new URL("http://www.apache.org/dist/tomcat/tomcat-6/v6.0.20/bin/apache-tomcat-6.0.20.zip"));

installer.install();

// (2) Create the Cargo Container instance wrapping our physical container

LocalConfiguration configuration = (LocalConfiguration) new DefaultConfigurationFactory()

.createConfiguration("tomcat6x"), ContainerType.INSTALLED, ConfigurationType.STANDALONE);

container = (InstalledLocalContainer) new DefaultContainerFactory()

.createContainer("tomcat6x", ContainerType.INSTALLED, configuration);

container.setHome(installer.getHome());

// (3) Statically deploy some WAR (optional)

WAR deployable = new WAR("./webapp-testing-webapp/target/webapp-testing-webapp-1.0/"); // .war works like a charm.

deployable.setContext("ROOT");

configuration.addDeployable(deployable);

// (4) Start the container

container.start();

I confirmed that the directory exists and is a valid exploded WAR. The same code snippet works great if I specify the path to the WAR file instead.

I tracked down the problem to TomcatCopyingInstalledLocalDeployer.deployExpandedWar:141. shouldCopyWars is false so super.deployExpandedWar(..) isn't called. I'm not explicitly setting shouldCopyWars to false; AbstractCatalinaStandaloneLocalConfiguration is doing that on line 185.

Any suggestions? Is this a bug or am I missing something?

Thanks,

Christian

PS: I'm using Cargo 1.0.

--
Christian Nelson -- (e) cnelson@... -- (m) 415-378-3988

CARGO 1.0.1

2009-09-21T07:35:47Z

Hello

Any plans for a CARGO 1.0.1 release?

Cheers

--

S. Ali Tokmen
savas-ali.tokmen@...

Office: +33 4 76 29 76 19
GSM: +33 66 43 00 555

Bull, Architect of an Open World TM
http://www.bull.com

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

Re: JOnAS link missing

2009-09-21T07:35:16Z

Hello

Matt Wringe a écrit :
> JOnAS link added
>

Thanks :)

> Please note that it is a wiki and fixes like this are encouraged.
>

You're absolutely right... And how do I log in to the wiki to edit the
page, I didn't see the link? I would gladly add the links for Geronimo,
Glassfish and jrun (which are also missing).

Cheers

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

Re: Problem on a multi-modules project

2009-09-20T23:21:08Z

On Sun, Sep 20, 2009 at 03:46:19PM -0700, niaouli wrote:
> I would like to be able to work directly from the parent module, in order to
> enable Hudson (my continuous integration engine) to deploy automatically
> this web application. You can see below my pom.xml files, for the parent and
> then the concerned module.
>

The easiest way I found to achieve this is to define execution in
submodule pom, and bind it to one of build phases. I.e. I did
something like:

<build>
<plugins>
<plugin>
<groupId>org.codehaus.cargo</groupId>
<artifactId>cargo-maven2-plugin</artifactId>
<version>1.0</version>
<configuration>
<container>
<containerId>geronimo1x</containerId>
<home>/usr/local/geronimo-jetty6-javaee5-2.1.4</home>
</container>
</configuration>
<executions>
<execution>
<id>redeploy</id>
<phase>install</phase>
<goals>
<goal>redeploy</goal>
</goals>
</execution>
</executions>
</plugin>
</plugins>
</build>
</project>

Now if you do mvn install (or any other goal that passes install
phase) for the master pom.xml it will execute cargo:redeploy for this
module.

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

Problem on a multi-modules project

2009-09-20T15:46:19Z

Hello,

I am using Cargo on a multi-module project.
Everything is perfect when I work on the module project : mvn clean install cargo:deployer-redeploy

But when I did the same in the parent project, I got an error : The plugin 'org.apache.maven.plugins:maven-cargo-plugin' does not exist or no valid version could be found
So I changed the line for : mvn clean install org.codehaus.cargo:cargo-maven2-plugin:deployer-redeploy
Then I got another problem : For all packaging other than war you need to configure the container you wishes to use.

I would like to be able to work directly from the parent module, in order to enable Hudson (my continuous integration engine) to deploy automatically this web application. You can see below my pom.xml files, for the parent and then the concerned module.

Thanks for your help. Regards,

Mickaël T.

---------------------

<project>
<modelVersion>4.0.0</modelVersion>
<groupId>nc.ird</groupId>
<artifactId>MyProject</artifactId>
<packaging>pom</packaging>
<name>MyProject</name>
<version>0.1-SNAPSHOT</version>
<modules>
<module>MyProject.domain</module>
<module>MyProject.service</module>
<module>MyProject.web</module>
</modules>

</project>

---------------------

<project>
<parent>
<artifactId>MyProject</artifactId>
<groupId>nc.ird</groupId>
<version>0.1-SNAPSHOT</version>
</parent>
<modelVersion>4.0.0</modelVersion>
<groupId>nc.ird</groupId>
<artifactId>MyProject.web</artifactId>
<packaging>war</packaging>
<name>MyProject.web</name>
<version>0.1-SNAPSHOT</version>
<properties>
<deploy.host>deployHost</deploy.host>
<deploy.port>8080</deploy.port>
<deploy.user>deployUser</deploy.user>
<deploy.password>deployPassword</deploy.password>
</properties>
<build>
<plugins>
<plugin>
<groupId>org.codehaus.cargo</groupId>
<artifactId>cargo-maven2-plugin</artifactId>
<configuration>
<container>
<containerId>tomcat6x</containerId>
<type>remote</type>
</container>
<configuration>
<type>runtime</type>
<properties>
<cargo.tomcat.manager.url>http://${deploy.host}:${deploy.port}/manager/</cargo.tomcat.manager.url>
<cargo.remote.username>${deploy.user}</cargo.remote.username>
<cargo.remote.password>${deploy.password}</cargo.remote.password>
</properties>
</configuration>
<deployer>
<type>remote</type>
<deployables>
<deployable>
<groupId>${project.groupId}</groupId>
<artifactId>${project.artifactId}</artifactId>
<type>war</type>
<pingURL>http://${deploy.host}:${deploy.port}/${parent.project.build.finalName}/</pingURL>
</deployable>
</deployables>
</deployer>
</configuration>
</plugin>
</plugins>
</build>

</project>

Re: Redeploying to running conainer with maven2 - is there a better way?

2009-09-18T09:42:43Z

I had the same issue and I got around that by using cargo:redeploy mojo instead of separate undeploy and deploy.

HTH

pisajew wrote:

Hello

I'm using cargo to deploy EAR to geronimo. I wanted to do "mvn
install" in the main directory of multimodule project and to have the
EAR module deployed as the result. So I bound cargo to install phase
in the pom.xml for EAR module, like this:

<plugin>
<groupId>org.codehaus.cargo</groupId>
<artifactId>cargo-maven2-plugin</artifactId>
<version>1.0</version>
<configuration>
<container>
<containerId>geronimo1x</containerId>
<home>/usr/local/geronimo-jetty6-javaee5-2.1.4</home>
</container>
</configuration>
<executions>
<execution>
<id>redeploy</id>
<phase>install</phase>
<goals>
<goal>undeploy</goal>
<goal>deploy</goal>
</goals>
</execution>
</executions>
</plugin>

This works well, if the application is deployed to server before doing
"mvn install". This does not need to be always true and if it's not
maven stops because it fails to undeploy the app. In such case I would
like to skip "undeploy" goal but run the "deploy" task. Is there any
way to configure cargo plugin so it will not report failure to maven
if it fails to undeploy the application? Or maybe there is a better
way to achieve what I want?

Regards,

Piotr

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

Redeploying to running conainer with maven2 - is there a better way?

2009-09-18T05:30:32Z

Hello

I'm using cargo to deploy EAR to geronimo. I wanted to do "mvn
install" in the main directory of multimodule project and to have the
EAR module deployed as the result. So I bound cargo to install phase
in the pom.xml for EAR module, like this:

<plugin>
<groupId>org.codehaus.cargo</groupId>
<artifactId>cargo-maven2-plugin</artifactId>
<version>1.0</version>
<configuration>
<container>
<containerId>geronimo1x</containerId>
<home>/usr/local/geronimo-jetty6-javaee5-2.1.4</home>
</container>
</configuration>
<executions>
<execution>
<id>redeploy</id>
<phase>install</phase>
<goals>
<goal>undeploy</goal>
<goal>deploy</goal>
</goals>
</execution>
</executions>
</plugin>

This works well, if the application is deployed to server before doing
"mvn install". This does not need to be always true and if it's not
maven stops because it fails to undeploy the app. In such case I would
like to skip "undeploy" goal but run the "deploy" task. Is there any
way to configure cargo plugin so it will not report failure to maven
if it fails to undeploy the application? Or maybe there is a better
way to achieve what I want?

Regards,

Piotr

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

Remote deploy on tomcat6 with hudson/maven2

2009-09-17T18:18:19Z

Hi,

I am trying to get a ROOT.war deployed to remote tomcat 6 instance. Here is the project structure

svnrepo
|
-- parent-project/trunk/pom.xml
-- project-a/trunk/pom.xml

Parent project pom contains cargo maven2 plugin and its configuration. For some odd reason the WAR name that gets deployed is neither the artifactId of the project-a nor is it the build/finalname of project-a. It seems like its a word which occurs in one of the dependencies of project-a!! Also, no matter what I put in the properties/context it always takes the name of the war as the context.

It is a mystery to me on how cargo is setting the war filename.

Any help will be appreciated.

Here is the config for cargo plugin

<plugin>
<inherited>true</inherited>
<groupId>org.codehaus.cargo</groupId>
<artifactId>cargo-maven2-plugin</artifactId>
<version>1.0</version>
<executions>
<execution>
<id>verify-deploy</id>
<phase>install</phase>
<goals>
<goal>deployer-redeploy</goal>
</goals>
</execution>
</executions>
<configuration>

<container>
<containerId>tomcat6x</containerId>
<type>remote</type>
</container>


<configuration>
<type>runtime</type>
<properties>
<cargo.tomcat.manager.url>http://${remote.tomcat.host}:${remote.tomcat.port}/manager </cargo.tomcat.manager.url>
<cargo.remote.username>username</cargo.remote.username>
<cargo.remote.password>password</cargo.remote.password>
</properties>
</configuration>


<deployer>
<type>remote</type>
<deployables>
<deployable>
<type>war</type>
<groupId>${pom.groupId}</groupId>
<artifactId>${pom.artifactId}</artifactId>
<properties>
<context>abc</context>
</properties>
</deployable>
</deployables>
</deployer>
</configuration>
</plugin>

Re: JOnAS link missing

2009-09-14T08:25:30Z

On Mon, 2009-09-14 at 15:08 +0200, S. Ali Tokmen wrote:
> Hello
>
> On the http://cargo.codehaus.org/Downloads page, some containers are
> missing (namely JOnAS but I think also others).

JOnAS link added

Please note that it is a wiki and fixes like this are encouraged.

> Can someone take a look?
>
> Cheers
>

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

JOnAS link missing

2009-09-14T06:08:48Z

Hello

On the http://cargo.codehaus.org/Downloads page, some containers are
missing (namely JOnAS but I think also others).

Can someone take a look?

Cheers

--

S. Ali Tokmen
savas-ali.tokmen@...

Office: +33 4 76 29 76 19
GSM: +33 66 43 00 555

Bull, Architect of an Open World TM
http://www.bull.com

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

Re: How to lower the JBoss logging level

2009-09-11T06:32:04Z

On Thu, 2009-09-10 at 22:41 +0200, David wrote:
> Hi,
>
>
> According to http://jira.codehaus.org/browse/CARGO-585, there is an
> undocumented workaround for setting the log4j logging level with the
> cargo maven plugin, but I do not see how to do it the Java Cargo API.

configuration.setProperty(GeneralPropertySet.LOGGING, [low, medium,
high])

but its a bit messed up right now and might still be a bit too verbose.
That bug report does have a work around listed.

>
> Right now, the JBoss 4.0.5 server that I'm starting with the Java
> Cargo API is extremely verbose, slowing down the startup process quite
> a lot :(
>
>
>
>
> Thanks in advance,
> David

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

How to lower the JBoss logging level

2009-09-10T13:41:04Z

Hi,

According to http://jira.codehaus.org/browse/CARGO-585, there is an undocumented workaround for setting the log4j logging level with the cargo maven plugin, but I do not see how to do it the Java Cargo API.

Right now, the JBoss 4.0.5 server that I'm starting with the Java Cargo API is extremely verbose, slowing down the startup process quite a lot :(

Thanks in advance,

David