gmane.comp.java.cargo.user

CARGO 1.2.2 available!

S. Ali Tokmen — 2012-05-21T18:26:22

Dear CARGO enthusiasts

After about 7 weeks after the last release, I decided we have enough
changes and fixed bugs in order to go ahead with CARGO 1.2.2. As for
what's new, the list is this time small (12 entries):

*Improvements and new features* (5)

  *
      o Jetty containers now support datasources (CARGO-1107
        <https://jira.codehaus.org/browse/CARGO-1107>)
      o Jetty 7.x standalone local container is now the default
        container for the CARGO Maven2/Maven3 plugin (CARGO-1106
        <https://jira.codehaus.org/browse/CARGO-1106>) and downloads its
        container via the artifactInstaller
      o The usage of an external jetty-env.xml file has finally been
        documented (CARGO-861 <https://jira.codehaus.org/browse/CARGO-861>)
      o The XML/properties replacement engine can now WARN when a
        replacement is not possible (instead of failing) (CARGO-1099
        <https://jira.codehaus.org/browse/CARGO-1099>)
      o Deployers (and mostly undeployers) can now intelligently ign

Using Cargo to start up Server in Integration test in maven project

MiB — 2012-05-04T12:51:23

I have set up a simple Maven 2 Spring MVC project and want to start by  
doing end to end integration testing in the form of simple short  
Acceptance tests. Everything in my project is set up properly enough  
to work when I run my integration tests with the server started inside  
of Eclipse. I use Tomcat 6.0.35 which is what is on the server, but  
for testing any container would do.

I'm using Surefire 2.8 excluding integration tests and let Failsafe  
2.12 run the integration tests.

As the tests does run though the server isn't starting up resulting in  
build success and test failure, I'm obviously missing some set up that  
would allow some action of Failsafe indirectly or directly to start up  
the server via Cargo. Failsafe executes the goals "integration-test"  
and "verify" and I want Cargo to start the server prior to running the  
integration tests and to stop the server when they're done.

I've read the documentation and several articles, but I'm obviously  
missing some details here. It would

NodeMerge question

Neo Qing — 2012-05-04T09:36:35

Hi, Dear Developers:
   I have questions about NodeMerge.
   I want to merge two wars, warA has a web.xml, it has element
<welcome-file-list>
    <welcome-file>index.html</welcome-file>
  </welcome-file-list>
the web.xml of warB  has element as below
 <welcome-file-list>
    <welcome-file>default.html</welcome-file>
      <welcome-file>test.jsp</welcome-file>
  </welcome-file-list>
 I want to merge welcome-file-list and without any information lost, how to
define the merge strategy?
Currently ,I'm using below
<tag name="welcome-file-list">
            <strategy name="NodeMerge">
            <welcome-file-list>
                <welcome-file>$left:welcome-file</welcome-file>
                <welcome-file>$right:welcome-file</welcome-file>
            </welcome-file-list>
            </strategy>
          </tag>
 result is
<welcome-file-list>
    <welcome-file>index.html</welcome-file>
    <welcome-file>default.html</welcome-file>
  </welcome-file-list>
but my expect is
<welcome-file-list>
    <welcome-file>ind

Failing to set JVM properties on Glassfish

Denis N. Antonioli — 2012-05-02T21:37:59

Hi

I'm using the maven cargo plugin 1.2.1.

I want to overwrite some properties during the deployment of my war to glasssfish 3.1, but this doesn't seem to work.

Does anyone got this working?

In my pom, I set:
              <plugin>
                   <groupId>org.codehaus.cargo</groupId>
                   <artifactId>cargo-maven2-plugin</artifactId>
                   <version>1.2.1</version>
                   <configuration>
                       <container>
                           <dependencies>
                               <dependency>
                                   <groupId>org.apache.derby</groupId>
                                   <artifactId>derby</artifactId>
                               </dependency>
                           </dependencies>
                           <systemProperties>
                               <derby.system.home>${project.build.directory}/derby</derby.system.home>
                               <hibernate.hbm2ddl.auto>create-drop</hibernate.hbm2ddl.auto>

NoClassDefFoundError with GlassFish 3.1.2

hoangx281283 — 2012-05-02T08:04:02

I encountered NoClassDefFoundError problem with Cargo/GlassFish 3.1.2 (i'm
using Ant to deploy the test)

The log message told me that my class, located under
deployed_war/WEB-INF/lib requires a class (a log library) located in
<sharedClasspath>but the web app classloader could not find such class.

Anyone has encountered the same problem as mine?

SSL?

Luis Montes — 2012-05-01T01:54:21

Is is possible to run cargo and listen on a secure port?  Was hoping to
test some oauth2 stuff which requies HTTPS.

Thanks,

Luis

Reload JSPs

Mansour Al Akeel — 2012-04-30T15:56:43

Hello all,
I am using cargo ant to run my webapp. This webapp, contains JSPs
files. When I modify these jsps under full tomcat
($TOMCAT_HOME/webapps/myApp/test.jsp),
I can see the modification when the page reload. With maven-tomcat the
same thing. Reloading is transparent.
With cargo ant, this is not the case. Is there some config I am
missing ? Here's mine:

  <cargo containerId="tomcat7x"
                   home="< at >{tomcat-home}"
                   output="< at >{tomcat-log-dir}/output.log"
                   log="< at >{tomcat-log-dir}/cargo.log"
                   action="run">
                <configuration home="< at >{tomcat-config-dir}">
                    <property name="cargo.servlet.port" value="8080"/>
                    <property name="cargo.logging" value="low"/>
                    <deployable type="war" file="${build.dir}">
                        <property name="context" value="${ant.project.name}"/>
                    </deployable>
                </configuration>
            </cargo>


Thank you.

---

ConcurrentModificationException when trying to merge xml file

MrProgrammer55 — 2012-04-27T21:26:37

I went ahead and posted this as a bug at Cargo's site, but I thought I'd post
a message here to see if anyone else has encountered this problem also?

https://jira.codehaus.org/browse/CARGO-1105
https://jira.codehaus.org/browse/CARGO-1105 

Quick summary of bug: Trying to merge 2 non web.xml xml files and get the
following error:

Caused by: java.util.ConcurrentModificationException
at java.util.AbstractList$Itr.checkForComodification(AbstractList.java:372)
at java.util.AbstractList$Itr.next(AbstractList.java:343)
at
org.codehaus.cargo.module.merge.DocumentMerger.merge(DocumentMerger.java:95)
at
org.codehaus.cargo.module.merge.DocumentMerger.performMerge(DocumentMerger.java:79)
at
org.codehaus.cargo.module.merge.DocumentStreamAdapter.performMerge(DocumentStreamAdapter.java:101)
... 25 more

Using Cargo 1.2.1. Please see link for more info.  Thanks for your time.
Chris

Customize log level for container

hoangx281283 — 2012-04-26T09:36:07

I wish to know how could we set log level on a group of classes for container
running in Cargo, something like

org.abc.xyz.level=FINEST

I have GlassFish started via Cargo, i tried to customize the log config of
orginal GlassFish. However, the log config is always replaced with one
provided by Cargo

Questions on GlassFish 3 with Cargo Ant

hoangx281283 — 2012-04-25T09:01:02

I defined extraClasspath via Ant configuration for GlassFish 3.1.2 container
but it did not work

         <cargo
         containerId="${cargo.container.id}"
         home="${test.cargo.home}"
         log="${cargo.log.dir}/cargo.${test.id}.start.log"
         ....
         <extraClasspath>
           <pathelement location="${correct path to my jar}" />
         </extraClasspath>
         ....

Did anyone encounter the same problem as mine?

I'm using Cargo 1.0.6, and i learnt through Cargo JIRA that Cargo 1.0.6
supports GlassFish 3.x

Use of "existing local configuration for installed Jetty container"

Shum, Adrian — 2012-04-24T03:46:25

Dear all,

 

I was trying to see if I can externalized the JNDI entry by 

providing an external jetty-env.xml 

(http://jira.codehaus.org/browse/CARGO-861)

 

I was then referred to 

https://jira.codehaus.org/browse/CARGO-1083

and I was told it should solve the problem.

 

However, I found difficulties in understanding how to

use this feature to archieve what I want.

 

I don't want Jetty to be pre-installed.  I want a my build

machine be able to just get the source, and it will install

and run Jetty by Cargo automatically, and run my integration

tests against it.  Therefore I don't want jetty-env.xml 

built into my WAR.  Instead, it will be a file provided externally.

 

Can anyone give me some direction on this?

 

Thanks

--

Best regards,

Adrian Shum

Multi-level Contexts failing on Tomcat 7

danhome — 2012-04-05T11:55:05

Apparently multi-level context paths were fixed as part of
https://jira.codehaus.org/browse/CARGO-734, but I'm not having any luck. 
Has anyone else has success getting multi-level contexts to work with Tomcat
7?

If I set the <context>secure#testapp</context> deployment fails with the
following error:

[INFO] [edDeployerDeployMojo] Resolved container artifact
org.codehaus.cargo:cargo-core-container-tomcat:jar:1.2.1 for container
tomcat7x
[DEBUG] Performing deployment action into [Tomcat 7.x Remote]...
[DEBUG] Initial deployable values: groupId = [com.testapp], artifactId =
[testapp], type = [war], location = [null]
[DEBUG] Searching for an artifact that matches
[com.testapp:testapp:war:null]...
[DEBUG] Checking artifact
[com.myapp.test:test-deployment-as01-tomcatsvr2:pom:null]...
[DEBUG] Checking artifact [com.testapp:testapp:war:null]...
[DEBUG] Computed deployable values: groupId = [com.testapp], artifactId =
[testapp], classifier = [null], type = [war], location =
[/Users/Joe/.m2/repo/com/testapp/testap

CARGO 1.2.1 is now available, and is not an April fool!

S. Ali Tokmen — 2012-03-31T22:07:25

Dear CARGO enthusiasts

CARGO 1.2.1 is now available; and no this is definitely not an April fool!

Of course, all of you are wondering what that release brings in... As
usual, we have a certain number of fixes and improvements; major
highlights are:

  * 12 bug fixes, be it for core components but also for containers.
  * CARGO now supports starting an installed local container
    independently from the starting instance (Java API, ANT or
    Maven2/Maven3 plugin); so that the started container can "outlive".
    This new feature is called spawning.
  * The Jetty container now supports existing local configuration.
  * JBoss 7.1.0 and 7.1.1 (Final versions) are supported.
  * The XML merger (i.e., uberwar) now does a much more careful work
    when it comes to merging duplicate XML entities.

To use this new version:

  * Users of the Java API and/or ANT tasks can download the CARGO
    uberjar and ANT tasks from the download page:
    http://cargo.codehaus.org/Downloads
  * Maven2/Maven3 users simply need

Logging settings

Dirk Mahler — 2012-03-29T11:23:42

Hi,

we're using the cargo maven plugin with JBoss 7.1.0.Final. We provide 
our own standalone.xml which is copied by cargo to the container 
configuration and afterwards processed by cargo for adjusting ports etc. 
This works fine so far.

Our problem is that cargo also adjusts the logging configuration by 
applying the values according to "cargo.logging" to the console handler 
and root logger. Is there a way to suppress this and just use the values 
as they are provided from "our" standalone.xml?

Regards

Dirk

Stopping container affects another module in maven parallel build

no1wantdthisname — 2012-03-20T17:42:13

I have multiple integration test modules that start up their own container.  

It works fine when running "mvn verify", but sometimes fails when running
"mvn -T 1C verify".  As far as I can tell, the stop goal of one module is
affecting the other.

Is there a way to prevent this while still being able to run in parallel?

Cargo Maven Plugin: Start permanently in another thread

eduardoh — 2012-03-13T20:17:41

I am trying to start an existing local Jetty with Cargo, using the maven
plugin.

My CI tool (Bamboo) has an agent in the server which executes the maven
goals to deploy my war, and restart the server.

The problem I am facing is:
1) If I use "cargo:start", the server is shut down as soon as the maven
finishes the build
2) If I use "cargo:run", the server starts, but my agent session gets
"locked"/busy since the cargo plugin is waiting for the CTRL+C user command
to finish the maven task.


I believe what I need is a bit of both: the server running in another
thread, so it doesn't lock the parent maven, but without shutting down when
the parent completes.


Is there any thoughts or possibilites in that direction?

Thanks for your usual assistance,
Eduardo

Encountering Exception when deploying in Jetty 7.2x ExistingInstallation

svu004 — 2012-03-06T19:35:18

Hi,

I am trying to deploy a war[say, mywebapp.war] in Jetty7.2x [which is
already installed on my host] and start Jetty container using the below pom.
[All that the pom contains is to have a dependency on the mywebapp.war,
deploy it in the container and start jetty]. 

I am encountering the below " java.lang.NumberFormatException" from Jetty
and Jetty shows up the usage... Any pointers or suggestion to solving the
issue will greatly help me.
Please let me know if there is something that I am missing in my pom.xml
[see below ] 

Note: I am using the 1.2.1-snapshot version that contains Eduardoh's fix for
supporting the Existing Installation Type. 



[INFO]
------------------------------------------------------------------------
[INFO] [talledLocalContainer] Jetty 7.x starting...
[INFO] [talledLocalContainer] Running Jetty As: "C:\Program
Files\Java\jdk1.6.0_
25\jre\bin\java.exe" -Xms128m -Xmx512m -XX:PermSize=48m -XX:MaxPermSize=128m
-Dj
etty.home=C:\test_jetty_home\jetty-distribution-7.2.2.v20101205 -DSTO

How can I deploy to running JBoss 7.1 using Cargo?

laredotornado — 2012-03-01T22:48:32

Hi,

I'm using Maven 3.0.3 and trying to deploy my app to a running JBoss 7.1
server, installed locally.  What dependencies do I need to include to make
this happen?  Here is my current Cargo configuration ...

<plugins>
<plugin>
<groupId>org.codehaus.cargo</groupId>
<artifactId>cargo-maven2-plugin</artifactId>
<version>1.1.3</version>
<configuration>
<container>
<containerId>jboss7x</containerId>
<type>remote</type>
</container>
</configuration>
<executions>
<execution>
<id>deploy</id>
<phase>install</phase>
<goals>
<goal>deploy</goal>
</goals>
</execution>
</executions>
</plugin>
</plugins>

And here is the error message I'm getting ...

[ERROR] Failed to execute goal
org.codehaus.cargo:cargo-maven2-plugin:1.1.3:deploy (deploy) on project
event-maven: Execution deploy of goal
org.codehaus.cargo:cargo-maven2-plugin:1.1.3:deploy failed: Failed to create
deployer with implementation class
org.codehaus.cargo.c

No datasource configuration generated

Serkan Erdur — 2012-03-01T13:09:41

Hi,

Below is my maven pom configuration.
I am running "clean integration-test" and in the end no datasource
configuration is produced in "tomcat/conf/" server.xml or context.xml. Otherwise
everything seems ok (oracle jar is copied into common/lib).
Anyone ideas?

Many thanks
                              <plugin>
<groupId>org.codehaus.cargo</groupId>
<artifactId>cargo-maven2-plugin</artifactId>
<version>1.2.0</version>
<executions>
<execution>
<id>start</id>
<phase>pre-integration-test</phase>
<goals>
<goal>start</goal>
</goals>
</execution>
<execution>
<id>stop</id>
<phase>post-integration-test</phase>
<goals>
<goal>stop</goal>
</goals>
</execution>
</executions>
<configuration>
<wait>false</wait>
<!-- Container Configuration -->
<container>
<containerId>tomcat6x</containerId>
<zipUrlInstaller>
<url>https://xxx/content/groups/global/tomcat/tomcat-
6/apache-tomcat/6.0.33/apache-tomcat-6.0.33.zip</url>
<proxy>
<host>xxx</host>
<port>8

No datasource configuration generated in server.xml.

serkan — 2012-03-01T12:48:52

Hi,

Below is my maven pom configuration.
I am running "clean integration-test" and in the end no datasource
configuration is produced in "tomcat/conf/server.xml". Otherwise
everything seems ok (oracle jar is copied into common/lib).
Anyone ideas?

Many thanks
<plugin>
<groupId>org.codehaus.cargo</groupId>
<artifactId>cargo-maven2-plugin</artifactId>
<version>1.1.4</version>
<executions>
<execution>
<id>start</id>
<phase>pre-integration-test</phase>
<goals>
<goal>start</goal>
</goals>
</execution>
<execution>
<id>stop</id>
<phase>post-integration-test</phase>
<goals>
<goal>stop</goal>
</goals>
</execution>
</executions>
<configuration>
<wait>false</wait>
<!-- Container Configuration -->
<container>
<containerId>tomcat6x</containerId>
<zipUrlInstaller>
<url>https://xxxx/content/groups/global/tomcat/tomcat-6/apache-tomcat/6.0.33/apache-tomcat-

Starting jetty with server configuration file

eduardoh — 2012-03-01T08:50:18

Hi there,

In our company, we have a common installation of jetty in the server, and
each application runs in a different instance of the common installation.

Deployment using maven cargo (Jetty 7x installed local deployment) is
working great - but stopping and starting the container after the deployment
has some problems, let me try to clarify.

Many properties, like jetty port, rmi port, jetty home, etc are different
for each application.
For the moment, the server admins have a file for each application which
loads these specific properties, which is called in their script before
calling the jetty.jar.

Obviously, we don't want to use same scripts to start/stop jetty, therefore
we want to use jetty + cargo capabilities to do similar.

Our initial thought was to have a specific start.ini for each app, where
they can load their variables, and all the configuration will be in the
server admin hands - not somewhere in the pom.xml of each app.
The only thing each application would have to know is the name (l