Mansour Al Akeel | 3 Feb 23:57
Picon

Run with tomcat7

I am trying to run an existing application using cargo ant.

The example given on the page http://cargo.codehaus.org/Ant+support

deletes the resulting exploded war, then creates a tomcat installation in the target dir. Therefore I am unable to see the application.

<property name="tomcat.home" value="/opt/tomcat"/>
    <property name="tomcatlog.dir" value="target"/>
    <property name="tomcatconfig.dir" value="target/tomcat"/>
    <property name="mywarfile" value="target/webapps/myWebapp"/>
   
    <taskdef resource="cargo.tasks">
    <classpath>
        <fileset dir="cargo">
        <include name="**/*.jar"/>
        </fileset>
    </classpath>
    </taskdef>
   
    <target name="cargostart" depends="war">
    <delete dir="${tomcatconfig.dir}" />
    <mkdir dir="${tomcatlog.dir}"/>
    <mkdir dir="${tomcatconfig.dir}"/>
    <echo message="Starting Cargo..."/>
    <echo message="Using tomcat.home = ${tomcat.home} "/>
    <echo message="Using war = ${mywarfile} "/>
    <!-- <echo message="Jars used = ${cargo-uberjar} , ${cargo-antjar}"/> -->
   
    <cargo containerId="tomcat7x" home="${tomcat.home}" output="${tomcatlog.dir}/output.log"
           log="${tomcatlog.dir}/cargo.log" action="run">
        <configuration home="${tomcatconfig.dir}">
        <property name="cargo.servlet.port" value="8080"/>
        <property name="cargo.logging" value="low"/>
        <deployable type="war" file="${mywarfile}"/>
        </configuration>
    </cargo>

    </target>


Should I generate the war after I start tomcat, or there's something I am missing ?




Dreher, Markus | 1 Feb 09:08
Picon

Duplicate entries when merging wars

Hi all,

 

i’m trying to merge 2 wars with cargo-maven2-plugin 1.2.0.

Merging context-params works as expected, but for filter-mappings, mime-mappings, servlet-mappings and security-constraints there are duplicate entries in the resulting web.xml.

 

Each of the source web.xml contains an entry

 

  <mime-mapping>

    <extension>js</extension>

    <mime-type>application/x-javascript</mime-type>

  </mime-mapping>

 

And

 

  <filter-mapping>

    <filter-name>Trinidad Filter</filter-name>

    <url-pattern>*.jsf</url-pattern>

  </filter-mapping>

 

In the resulting web.xml there are 2 entries for mime-mapping and filter-mapping.

 

For servlet and filter elements this is not the case.

 

Can anybody give me a hint?

 

Thanks a lot.

 

Markus

40 Jahre DZBW

Herzlichen Dank unseren Kunden und Partnern. Wir freuen uns auf die gemeinsame Fortsetzung der konstruktiven, vertrauensvollen Zusammenarbeit.

Ihre Datenzentrale Baden-W

tante anni | 30 Jan 17:20
Picon

[MAVEN]"start" goal ignores configuration "run" works fine


i am on my first trip with cargo (maven plugin) - mvn clean verify
org.codehaus.cargo:cargo-maven2-plugin:run is working out of the box - impressive. But the next step
was to get all configuration into the pom so i
set
			<plugin>				<groupId>org.codehaus.cargo</groupId>				<artifactId>cargo-maven2-plugin</artifactId>				<version>1.1.4</version>				<!--
minimal configuration to let adb run (mvn package
org.codehaus.cargo:cargo-maven2-plugin:run) 					in a local tomcat -->				<configuration>					<containerId>tomcat7x</containerId>					<containerUrl>http://archive.apache.org/dist/tomcat/tomcat-7/v7.0.16/bin/apache-tomcat-7.0.16.zip					</containerUrl>					<configuration>						<properties>							<cargo.servlet.port>1718</cargo.servlet.port>						</properties>					</configuration>				</configuration>			</plugin>
I also created an profile that is renaming the war to ${project.artifactId} (without version)
so i
added 
					<plugin>						<groupId>org.codehaus.cargo</groupId>						<artifactId>cargo-maven2-plugin</artifactId>						<configuration>							<configuration>								<deployables>									<!--
ci profile has no standard war-name, so war must be spezified -->									<deployable>										<location>${project.build.directory}\${project.artifactId}.war</location>									</deployable>								</deployables>							</configuration>						</configuration>					</plugin>
to appropriate part of pom.

--> "mvn clean verify org.codehaus.cargo:cargo-maven2-plugin:run" is still working fine, now the app
is deployed on tomcat.
But "mvn clean verify org.codehaus.cargo:cargo-maven2-plugin:start" tells "No container defined,
using a default [jetty6x, embedded] container" (it does not matter if the profile is active)
So how to get this simple config work with "start"?
thx in advance

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

    http://xircles.codehaus.org/manage_email

S. Ali Tokmen | 24 Jan 19:42
Gravatar

CARGO 1.2.0 now available!

Dear CARGO enthusiasts

First of all, happy New Year!

Since the last release of CARGO a bit more than one month and a half ago, we have had the opportunity of fixing some bugs and adding the functionalities:

  • CARGO Maven2/Maven3 plugin fixes and improvements:
    • ContainerStopMojo now can resolve dependencies with scope <test>, the same way ContainerRunMojo and ContainerStartMojo can (CARGO-1069 and CARGO-527).
    • The functional-tests artifact of the Separate Functional Test Module Archetype now uses packaging=jar and is compatible with m2e (CARGO-1065).
    • The CARGO plugin now resolves the required container JARs automatically (CARGO-975), meaning that if you're for example only using CARGO with the Jetty container than the other containers' JARs will not be downloaded.
  • Fixed a bug where the JSR-88 deployers' (used by the GlassFish remote deployer) undeploy method ignored the EAR's name ( CARGO-1076).
  • All CARGO JBoss containers, from the 10-year-old JBoss 3.x to the brand-new JBoss 7.1.x, now support datasources (CARGO-426). You can therefore now use CARGO to deploy datasources to any JBoss container; the bigger advantage being that the datasource definitions don't need to change between JBoss versions nor between all containers that CARGO can deploy datasources to.
  • The JOnAS remote deployer now works with Windows for XML deployment plans (CARGO-1067).
  • The Resin container has been improved:
  • Last but not least, the new XML replacement API introduced in CARGO 1.1.4, which avoids having CARGO-specific container configuration files in the distribution, is now used more extensively; as the Jetty (CARGO-1060), Resin (CARGO-1075) and Tomcat (CARGO-1061) container also make use of it.
    • This way, not only we won't have to maintain these CARGO-specific files manually anymore, but also new versions will be supported "out of the box" and CARGO will also work with different flavours of containers.

CARGO 1.2.0 is therefore now ready. Please note that on the API side, this new minor version comes with some behavioural changes and the removal of some elements (which have been deprecated for over 6 months now):

  • To achieve automatic resolution of container JARs in the Maven2/Maven3 container, a small change has been done in the ResourceUtils: it now loads resources using a class loader (as opposed to a class, which was the case in the past), hence AbstractLocalConfiguration.RESOURCE_PATH has been changed from "/org/codehaus/cargo/container/internal/resources/" to "org/codehaus/cargo/container/internal/resources/" (without the slash at the beginning). If your code uses the same constant, make sure you update it properly.
  • The Deployable.isExpanded* and AbstractCopyingInstalledLocalDeployer.setShouldDeployExpanded*s methods have been removed (CARGO-905 and CARGO-940). As a replacement:
    • The Deployable type has a generic isExpanded method.
    • AbstractCopyingInstalledLocalDeployer has a generic method setShouldDeployExpanded with two arguments.
  • File handling methods that manipulate texts now need to specify the encoding (CARGO-909).
  • In the Maven2/Maven3 plugin, the <zipUrlInstaller> and <artifactInstaller> don't have the <installDir> attribute anymore, replaced by <downloadDir> and <extractDir> attributes (CARGO-916).
  • TomcatPropertySet.MANAGER_URL (i.e. cargo.tomcat.manager.url) has been removed (CARGO-965), please use the generic RemotePropertySet.URI (i.e. cargo.remote.uri) instead.

You can access the full release notes by visiting https://jira.codehaus.org/secure/ReleaseNote.jspa?version=17088&styleName=Html&projectId=10730

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 to change the plugin's <version> to 1.2.0, and Maven2/Maven3 will download the new version automatically.

Please share your good (and bad) findings on the user-z8XaHfFCYGOxIXFVlbCvtR2eb7JE58TQ@public.gmane.org mailing list.

Enjoy!

-- S. Ali Tokmen http://ali.tokmen.com/ GSM (ch): +41 79 207 29 22 [Swisscom] GSM (fr): +33 7 70 10 33 79 [Virgin Mobile] GSM (tr): +90 555 266 52 73 [Avea] My AIM, ICQ, MSN Messenger and Yahoo IM contact details are on http://contact.ali.tokmen.com
ODB | 19 Jan 21:43
Gravatar

maven glassfish undeploy EAR issue


When calling cargo:undeploy the setting
<deployer><deployables><deployable><properties><name> is ignored. 
The plugin tries to undeploy the artifact with its original name, causing an
error.
Could this be a bug?

Environment: Maven 3.0.3, cargo-maven2-plugin 1.1.4 and 1.2.1-SNAPSHOT,
Glassfish 3.1.1

--

-- 
View this message in context: http://old.nabble.com/maven-glassfish-undeploy-EAR-issue-tp33170556p33170556.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

ODB | 19 Jan 21:41
Gravatar

maven glassfish undeploy issue


When calling cargo:undeploy the setting
<deployer><deployables><deployable><properties><>
--

-- 
View this message in context: http://old.nabble.com/maven-glassfish-undeploy--issue-tp33170533p33170533.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

Tomasz Kaczanowski | 13 Jan 10:39
Picon
Favicon

test classpath (spring resources) for JBoss

Hi All,

trying to run integration tests on JBoss 7. Previously did it on Jetty, 
using useTestClasspath so all test Spring configuration files 
(src/test/resources) were available during runtime. How can I achieve 
the same effect using Maven Cargo plugin? Is there any configuration 
option I should use? (tried to find it in documentation but failed).

Or maybe for JBoss I should generate a different war which includes 
resources from src/test/resources instead of src/main/resources?

-- 
Tomasz Kaczanowski
Senior Software Engineer

Software Mind SA| Where Quality Meets the Future
ul. Bociana 22a
31-231 Krakow
Poland
Tel. +48 12 252 34 00
Fax: +48 12 252 34 01
tomasz.kaczanowski@...
skype: tkaczanowski_sm
http://www.softwaremind.pl

Software Mind SA based in Krakow at ul. Bociana  22A, 31-231 Krakow
NIP 9452012822, seed capital PLN 500,000.00 (fully paid up)
District Court Kraków Śródmieście, XI Economics Department
of the National Court Register, KRS 0000300409

****************************** LEGAL DISCLAIMER*************************
This email may contain confidential and privileged material for the
sole use of the intended recipient(s). Any review, use, retention,
distribution or disclosure by others is strictly prohibited. If you are
not the intended recipient (or authorized to receive for the
recipient), please contact the sender by reply email and delete all
copies of this message. Also, email is susceptible to data corruption,
interception, tampering, unauthorized amendment and viruses. We only
send and receive emails on the basis that we are not liable for any
such corruption, interception, tampering, amendment or viruses or any
consequence thereof.

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

    http://xircles.codehaus.org/manage_email

Dirk Mahler | 3 Jan 11:47
Favicon

NPE while deploying to JBoss AS 6.1.0.Final

Just in case anyone running in the same troubles as we did: We are using 
maven cargo plugin to deploy to JBoss AS 6.1.0.Final and we faced the 
following exception while starting JBOSS AS on some of our developer's 
workstations:

11:11:46,637 ERROR [org.jboss.kernel.plugins.dependency.AbstractKernelController] Error
installing to Create:
name=vfs:///C:/development/work/cargo/default/deploy/application.ear-2.3.7.3-SNAPSHOT.ear_WeldBootstrapBean
state=Configured: java.lang.NullPointerException
         at org.jboss.weld.util.ApiAbstraction.annotationTypeForName(ApiAbstraction.java:86) [:6.1.0.Final]
         at org.jboss.weld.ejb.EJBApiAbstraction.<init>(EJBApiAbstraction.java:36) [:6.1.0.Final]
         at org.jboss.weld.bootstrap.BeanDeployment.<init>(BeanDeployment.java:100) [:6.1.0.Final]
         at org.jboss.weld.bootstrap.WeldBootstrap$DeploymentVisitor.visit(WeldBootstrap.java:185) [:6.1.0.Final]
         at org.jboss.weld.bootstrap.WeldBootstrap$DeploymentVisitor.visit(WeldBootstrap.java:197) [:6.1.0.Final]
         at org.jboss.weld.bootstrap.WeldBootstrap$DeploymentVisitor.visit(WeldBootstrap.java:156) [:6.1.0.Final]
         at org.jboss.weld.bootstrap.WeldBootstrap.startContainer(WeldBootstrap.java:293) [:6.1.0.Final]
         at
org.jboss.weld.integration.deployer.env.helpers.BootstrapBean.initialize(BootstrapBean.java:106) [:6.1.0.Final]

After heavy searching the cause it revealed that the problem was the 
directory which was specified for cargo (in our case it is a user 
defined setting) - there seems to be a problem with case sensitivity 
with JBOSS AS on Windows machines, you must use the name of the 
directory as it is reported by the file system, see 
https://issues.jboss.org/browse/JBAS-9465.

Regards

Dirk

-- 
-----------------------------------------------------------------
buschmais GbR
Inhaber  Torsten Busch, Frank Schwarz, Dirk Mahler, Tobias Israel
Adresse  buschmais GbR, Leipziger Straße 93, 01127 Dresden
Telefon  +49 (0) 351 3209 23-0
Fax      +49 (0) 351 3209 23-29
Mobil    +49 (0) 177 313 7411
E-Mail   dirk.mahler@...
Internet http://www.buschmais.com
-----------------------------------------------------------------

Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte
Informationen. Wenn Sie diese E-Mail irrtümlich erhalten haben,
bitten wir Sie diese E-Mail umgehend zu löschen. Das unerlaubte
Kopieren sowie die unbefugte Weitergabe dieser E-Mail ist nicht
gestattet.

This e-mail may contain confidential or privileged information.
If you are not the intended recipient we kindly request you to
delete this e-mail immediately. Any unauthorized copying,
disclosure or distribution of the material in this e-mail is
strictly forbidden.

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

    http://xircles.codehaus.org/manage_email

Aston C | 23 Dec 21:52
Picon

JBoss standalone Hot Deployment...


Excuse me for the newbie question...

I am trying a very simple case of deploying a servlet to a local JBoss.  The
following code did copy the FOOPublisher.war file to JBoss's deploy folder. 
However, the deploy() method never return and the FOOPublisher.war never get
expanded to the JBoss' deploy folder.

Is there anywhere I can find samples of different hot deployments
(standalone or remote) using java only?

Ultimately, I would like to deploy to other web server WebSphere (I know it
is not available yet...), WebLogic, Tomcat etc but I want to try out with
JBoss to evaluate if cargo is the right tool for our project.

Many thanks in advance.

-Aston

public class JBoss51xDeployer {

	    /**
	     * @param args the command line arguments
	     */
	    public static void main(String[] args) {
	    	
	    	loadJBossJars();
	    	
	    	ConfigurationFactory cfactory = new DefaultConfigurationFactory();
	    	
	    	Configuration configuration = (Configuration)
cfactory.createConfiguration(JBoss51xRemoteContainer.ID,
ContainerType.REMOTE, ConfigurationType.RUNTIME);
	    	

	        configuration.setProperty(RemotePropertySet.USERNAME, "admin");
	        configuration.setProperty(RemotePropertySet.PASSWORD, "admin");
	        configuration.setProperty(ServletPropertySet.PORT, "8080");
	    	
	    	
	        JBoss51xRemoteContainer container = new
JBoss51xRemoteContainer((RuntimeConfiguration) configuration);
	        
	        DeployableFactory factory = new DefaultDeployableFactory();
	        
	        WAR war = (WAR) factory.createDeployable(container.getId(),
"D:/Applications/my_deploy/FOOPublisher.war", DeployableType.WAR);
	        
	        System.err.println("** Container started? = " +
container.getState().isStarted());
	        
	        Deployer deployer = new JBoss51xRemoteDeployer(container);
	        
	        try {
	        	deployer.deploy(war, new URLDeployableMonitor(new
URL("http://localhost:8080/FOOPublisher/main")));
	        } catch (Exception e) {
	        	e.printStackTrace();
	        }
	        
	    }

--

-- 
View this message in context: http://old.nabble.com/JBoss-standalone-Hot-Deployment...-tp33030127p33030127.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

Aston C | 22 Dec 14:33
Picon

Websphere support?


Hi,

I know this question has been asked many times but I still can't find a
definitely answer anywhere.  Can I deploy my servlet to WebSphere?  Is there
a WebSphere container?

Thanks.

--

-- 
View this message in context: http://old.nabble.com/Websphere-support--tp33023708p33023708.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

Tyler Bronder | 19 Dec 23:19
Favicon
Gravatar

Cargo 1.1.4 error when stopping a test scoped Jetty container

We're using maven 2.2.1 with cargo on REST client & server Java packages, let's call it foo (all the pom goodness will be below). It's got separate foo-client and foo-server projects, and the client's integration test starts up an instance of the foo-server. When using version 1.1.3 of cargo, this works fine, but on 1.1.4 I get the following error when running the cargo:stop goal: 
  Artifact [com.opower:foo-server:war] is not a dependency of the project.

Can anybody help point me at the cause and a decent solution to this issue? I've found two workarounds for this issue, neither of which feels like an ideal solution:
 1. adding a "<version>1.1.3</version>" specifier to cargo's <plugin> block causes the build to work fine
 2. removing the cargo:stop goal and letting maven forcefully shut it down also works

I'm a bit of a maven n00b and I hope that I've included enough information to be helpful without writing a novel... if you scroll you'll see the foo-client pom, the maven output (v1.1.4), the maven output using version 1.1.3 with no failure, and finally the foo-server pom.

-Tyler

The project is set up with a parent pom.xml and the following child projects:

foo/
  foo-parent/
  foo-server/
  foo-client/


foo-client's pom.xml:

<?xml version="1.0" encoding="UTF-8"?>

    <modelVersion>4.0.0</modelVersion>
    <parent>
        <groupId>com.opower</groupId>
        <artifactId>foo-parent</artifactId>
        <version>1.6.0-SNAPSHOT</version>
        <relativePath>../foo-parent</relativePath>
    </parent>

    <artifactId>foo-client</artifactId>
    <packaging>jar</packaging>
    <version>1.6.0-SNAPSHOT</version>
    <name>Foo Service Client</name>

    <dependencies>
        <dependency>
            <groupId>${project.groupId}</groupId>
            <artifactId>foo-core</artifactId>
            <version>${project.version}</version>
        </dependency>
        <dependency>
            <groupId>com.opower</groupId>
            <artifactId>foo-server</artifactId>
            <version>${project.version}</version>
            <type>war</type>
            <scope>test</scope>
        </dependency>
        <dependency>
            <groupId>junit</groupId>
            <artifactId>junit</artifactId>
            <scope>test</scope>
        </dependency>
    </dependencies>
    <build>
        <plugins>
            <plugin>
                <groupId>org.codehaus.cargo</groupId>
                <artifactId>cargo-maven2-plugin</artifactId>
                <configuration>
                    <container>
                        <containerId>jetty6x</containerId>
                        <type>embedded</type>
                    </container>
                    <configuration>
                        <deployables>
                            <deployable>
                                <properties>
                                    <context>/</context>
                                </properties>
                                <groupId>com.opower</groupId>
                                <artifactId>foo-server</artifactId>
                                <type>war</type>
                            </deployable>
                        </deployables>
                    </configuration>
                    <wait>false</wait>
                </configuration>
                <executions>
                    <execution>
                        <id>start-container</id>
                        <phase>pre-integration-test</phase>
                        <goals>
                            <goal>start</goal>
                        </goals>
                    </execution>
                    <execution>
                        <id>stop-container</id>
                        <phase>post-integration-test</phase>
                        <goals>
                            <goal>stop</goal>
                        </goals>
                    </execution>
                </executions>
            </plugin>
        </plugins>
    </build>
</project>


Console output from running a build:
[INFO] Scanning for projects...
[INFO] ------------------------------------------------------------------------
[INFO] Building Foo Service Client
[INFO]    task-segment: [clean, install]
[INFO] ------------------------------------------------------------------------
[INFO] [clean:clean {execution: default-clean}]
[INFO] Deleting directory /opt/git/shared/foo/foo-client/target
[INFO] [svn-revision-number:revision {execution: default}]
[INFO] inspecting /opt/git/shared/foo/foo-client
[INFO] [resources:resources {execution: default-resources}]
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 1 resource
[INFO] skip non existing resourceDirectory /opt/git/shared/foo/foo-client/version
[INFO] skip non existing resourceDirectory /opt/git/shared/foo/foo-client/db/patches
[INFO] skip non existing resourceDirectory /opt/git/shared/foo/foo-client/db/postpatches
[INFO] skip non existing resourceDirectory /opt/git/shared/foo/foo-client/db/ami_schema
[INFO] [compiler:compile {execution: default-compile}]
[INFO] Compiling 7 source files to /opt/git/shared/foo/foo-client/target/classes
[INFO] [checkstyle:checkstyle {execution: checkstyle}]
[INFO] Starting audit...
Audit done.

[INFO] [scala:compile {execution: default}]
[INFO] Checking for multiple versions of scala
[INFO] includes = [**/*.scala,]
[INFO] excludes = []
[WARNING] No source files found.
[INFO] [resources:testResources {execution: default-testResources}]
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 19 resources
[INFO] Copying 1 resource
[INFO] [compiler:testCompile {execution: default-testCompile}]
[INFO] Compiling 2 source files to /opt/git/shared/foo/foo-client/target/test-classes
[INFO] [scala:testCompile {execution: default}]
[INFO] Checking for multiple versions of scala
[INFO] includes = [**/*.scala,]
[INFO] excludes = []
[WARNING] No source files found.
[INFO] [surefire:test {execution: default-test}]
[INFO] Surefire report directory: /opt/git/shared/foo/foo-client/target/surefire-reports

<unit tests omitted>

[INFO] [jar:jar {execution: default-jar}]
[INFO] Building jar: /opt/git/shared/foo/foo-client/target/foo-client-1.6.0-SNAPSHOT.jar
[INFO] Preparing source:jar
[WARNING] Removing: jar from forked lifecycle, to prevent recursive invocation.
[INFO] [svn-revision-number:revision {execution: default}]
[INFO] inspecting /opt/git/shared/foo/foo-client
[WARNING] the "artifact.svn.info.repository" property is already defined, its value will be overwritten. Consider another value for the entry properties prefix.
[WARNING] the "artifact.svn.info.path" property is already defined, its value will be overwritten. Consider another value for the entry properties prefix.
[WARNING] the "artifact.svn.info.revision" property is already defined, its value will be overwritten. Consider another value for the entry properties prefix.
[WARNING] the "artifact.svn.info.mixedRevisions" property is already defined, its value will be overwritten. Consider another value for the entry properties prefix.
[WARNING] the "artifact.svn.info.committedRevision" property is already defined, its value will be overwritten. Consider another value for the entry properties prefix.
[WARNING] the "artifact.svn.info.committedDate" property is already defined, its value will be overwritten. Consider another value for the entry properties prefix.
[WARNING] the "artifact.svn.info.status" property is already defined, its value will be overwritten. Consider another value for the entry properties prefix.
[WARNING] the "artifact.svn.info.specialStatus" property is already defined, its value will be overwritten. Consider another value for the entry properties prefix.
[INFO] [source:jar {execution: attach-sources}]
[INFO] Building jar: /opt/git/shared/foo/foo-client/target/foo-client-1.6.0-SNAPSHOT-sources.jar
[INFO] [cargo:start {execution: start-container}]
[INFO] [beddedLocalContainer] Jetty 6.x Embedded starting...


<server startup and test output lines omitted>

Tests run: 9, Failures: 0, Errors: 0, Skipped: 0

[INFO] [cargo:stop {execution: stop-container}]
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Artifact [com.foo-server:war] is not a dependency of the project.
[INFO] ------------------------------------------------------------------------
[INFO] For more information, run Maven with the -e switch
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 19 seconds
[INFO] Finished at: Mon Dec 19 17:02:13 EST 2011
[INFO] Final Memory: 76M/145M
[INFO] ------------------------------------------------------------------------
2011-12-19 17:02:13.583:INFO::Shutdown hook executing
2011-12-19 17:02:13.583:INFO::Stopped SelectChannelConnector <at> 0.0.0.0:8080
2011-12-19 17:02:13.590:INFO:/:Closing Spring root WebApplicationContext
2011-12-19 17:02:13,590 INFO  [Shutdown] [] [r.spring.WebApplicationContext] Closing Root WebApplicationContext: startup date [Mon Dec 19 17:02:09 EST 2011]; root of context hierarchy
2011-12-19 17:02:13,590 DEBUG [Shutdown] [] [r.spring.WebApplicationContext] Publishing event in Root WebApplicationContext: org.springframework.context.event.ContextClosedEvent[source=Root WebApplicationContext: startup date [Mon Dec 19 17:02:09 EST 2011]; root of context hierarchy]
2011-12-19 17:02:13.608:INFO:/:Shutting down log4j
log4j: [/private/var/folders/5g/_jfmsv892jl_3dcx3rvsy9xc0000gp/T/foo.server.1.6.0.SNAPSHOT.war____.gqkpbp/webapp/WEB-INF/classes/config/log4j.properties] does not exist.
2011-12-19 17:02:13.742:INFO::Shutdown hook complete


By specifying the 1.1.3 version of the cargo plugin, the same build cycle succeeds as shown here:
$ mvn clean install
[INFO] Scanning for projects...
[INFO] ------------------------------------------------------------------------
[INFO] Building Foo Service Client
[INFO]    task-segment: [clean, install]
[INFO] ------------------------------------------------------------------------
Unauthorized access prohibited. See http://opower.com/Warning.txt
[INFO] Unable to find resource 'org.codehaus.cargo:cargo-maven2-plugin:pom:1.1.3' in repository opower_releases (scp://mvn.opower.com/opt/releases)
[INFO] Unable to find resource 'org.codehaus.cargo:cargo-maven2-plugin:pom:1.1.3' in repository scala-tools.org (http://scala-tools.org/repo-releases)
      
Unauthorized access prohibited. See http://opower.com/Warning.txt
[INFO] Unable to find resource 'org.codehaus.cargo:cargo-maven2-plugin:maven-plugin:1.1.3' in repository opower_releases (scp://mvn.opower.com/opt/releases)
[INFO] Unable to find resource 'org.codehaus.cargo:cargo-maven2-plugin:maven-plugin:1.1.3' in repository scala-tools.org (http://scala-tools.org/repo-releases)
       
[INFO] [clean:clean {execution: default-clean}]
[INFO] Deleting directory /opt/git/shared/foo/foo-client/target
[INFO] [svn-revision-number:revision {execution: default}]
[INFO] inspecting /opt/git/shared/foo/foo-client
[INFO] [resources:resources {execution: default-resources}]
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 1 resource
[INFO] skip non existing resourceDirectory /opt/git/shared/foo/foo-client/version
[INFO] skip non existing resourceDirectory /opt/git/shared/foo/foo-client/db/patches
[INFO] skip non existing resourceDirectory /opt/git/shared/foo/foo-client/db/postpatches
[INFO] skip non existing resourceDirectory /opt/git/shared/foo/foo-client/db/ami_schema
[INFO] [compiler:compile {execution: default-compile}]
[INFO] Compiling 7 source files to /opt/git/shared/foo/foo-client/target/classes
[INFO] [checkstyle:checkstyle {execution: checkstyle}]
[INFO] Starting audit...
Audit done.

[INFO] [scala:compile {execution: default}]
[INFO] Checking for multiple versions of scala
[INFO] includes = [**/*.scala,]
[INFO] excludes = []
[WARNING] No source files found.
[INFO] [resources:testResources {execution: default-testResources}]
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 19 resources
[INFO] Copying 1 resource
[INFO] [compiler:testCompile {execution: default-testCompile}]
[INFO] Compiling 2 source files to /opt/git/shared/foo/foo-client/target/test-classes
[INFO] [scala:testCompile {execution: default}]
[INFO] Checking for multiple versions of scala
[INFO] includes = [**/*.scala,]
[INFO] excludes = []
[WARNING] No source files found.
[INFO] [surefire:test {execution: default-test}]
[INFO] Surefire report directory: /opt/git/shared/foo/foo-client/target/surefire-reports

<tests omitted>

[INFO] [jar:jar {execution: default-jar}]
[INFO] Building jar: /opt/git/shared/foo/foo-client/target/foo-client-1.6.0-SNAPSHOT.jar
[INFO] Preparing source:jar
[WARNING] Removing: jar from forked lifecycle, to prevent recursive invocation.
[INFO] [svn-revision-number:revision {execution: default}]
[INFO] inspecting /opt/git/shared/foo/foo-client
[WARNING] the "artifact.svn.info.repository" property is already defined, its value will be overwritten. Consider another value for the entry properties prefix.
[WARNING] the "artifact.svn.info.path" property is already defined, its value will be overwritten. Consider another value for the entry properties prefix.
[WARNING] the "artifact.svn.info.revision" property is already defined, its value will be overwritten. Consider another value for the entry properties prefix.
[WARNING] the "artifact.svn.info.mixedRevisions" property is already defined, its value will be overwritten. Consider another value for the entry properties prefix.
[WARNING] the "artifact.svn.info.committedRevision" property is already defined, its value will be overwritten. Consider another value for the entry properties prefix.
[WARNING] the "artifact.svn.info.committedDate" property is already defined, its value will be overwritten. Consider another value for the entry properties prefix.
[WARNING] the "artifact.svn.info.status" property is already defined, its value will be overwritten. Consider another value for the entry properties prefix.
[WARNING] the "artifact.svn.info.specialStatus" property is already defined, its value will be overwritten. Consider another value for the entry properties prefix.
[INFO] [source:jar {execution: attach-sources}]
[INFO] Building jar: /opt/git/shared/foo/foo-client/target/foo-client-1.6.0-SNAPSHOT-sources.jar
[INFO] [cargo:start {execution: start-container}]
[INFO] [beddedLocalContainer] Jetty 6.x Embedded starting...

<server startup and integration tests omitted>

[INFO] [cargo:stop {execution: stop-container}]
[INFO] [beddedLocalContainer] Jetty 6.x Embedded is stopping...
2011-12-19 17:16:24.035:INFO::Stopped SelectChannelConnector <at> 0.0.0.0:8080
2011-12-19 17:16:24.652:INFO:/:Closing Spring root WebApplicationContext
2011-12-19 17:16:24,652 INFO  [Thread-22] [] [r.spring.WebApplicationContext] Closing Root WebApplicationContext: startup date [Mon Dec 19 17:16:20 EST 2011]; root of context hierarchy
2011-12-19 17:16:24,653 DEBUG [Thread-22] [] [r.spring.WebApplicationContext] Publishing event in Root WebApplicationContext: org.springframework.context.event.ContextClosedEvent[source=Root WebApplicationContext: startup date [Mon Dec 19 17:16:20 EST 2011]; root of context hierarchy]
2011-12-19 17:16:24.671:INFO:/:Shutting down log4j
log4j: [/private/var/folders/5g/_jfmsv892jl_3dcx3rvsy9xc0000gp/T/Jetty_0_0_0_0_8080_foo.server.1.6.0.SNAPSHOT.war____.gqkpbp/webapp/WEB-INF/classes/config/log4j.properties] does not exist.
[INFO] [beddedLocalContainer] Jetty 6.x Embedded is stopped
[INFO] [install:install {execution: default-install}]
[INFO] Installing /opt/git/shared/foo/foo-client/target/foo-client-1.6.0-SNAPSHOT.jar to /opt/.m2repository/com/opower/foo-client/1.6.0-SNAPSHOT/foo-client-1.6.0-SNAPSHOT.jar
[INFO] Installing /opt/git/shared/foo/foo-client/target/foo-client-1.6.0-SNAPSHOT-sources.jar to /opt/.m2repository/com/opower/foo-client/1.6.0-SNAPSHOT/foo-client-1.6.0-SNAPSHOT-sources.jar
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESSFUL
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 29 seconds
[INFO] Finished at: Mon Dec 19 17:16:31 EST 2011
[INFO] Final Memory: 73M/142M
[INFO] ------------------------------------------------------------------------
2011-12-19 17:16:32.057:INFO::Shutdown hook executing
2011-12-19 17:16:32.057:INFO::Shutdown hook complete


And as a final postscript, the foo-server POM:

    <modelVersion>4.0.0</modelVersion>
    
    <parent>
        <groupId>com.opower</groupId>
        <artifactId>foo-parent</artifactId>
        <version>1.6.0-SNAPSHOT</version>
        <relativePath>../foo-parent</relativePath>
    </parent>

    <artifactId>foo-server</artifactId>
    <packaging>war</packaging>
    <name>Foo Server</name>
    <version>1.6.0-SNAPSHOT</version>
    <url>http://maven.apache.org</url>

    <dependencies>
        <dependency>
            <groupId>${project.groupId}</groupId>
            <artifactId>foo-core</artifactId>
            <version>${project.version}</version>
        </dependency>

        <dependency>
            <groupId>org.jboss.resteasy</groupId>
            <artifactId>resteasy-jaxrs</artifactId>
        </dependency>
        <dependency>
            <groupId>org.jboss.resteasy</groupId>
            <artifactId>resteasy-spring</artifactId>
        </dependency>
        <dependency>
            <groupId>org.codehaus.jackson</groupId>
            <artifactId>jackson-jaxrs</artifactId>
        </dependency>
        <dependency>
            <groupId>junit</groupId>
          <artifactId>junit</artifactId>
        </dependency>
    </dependencies>

    <build>
      <plugins>
        <plugin>
          <groupId>org.mortbay.jetty</groupId>
          <artifactId>maven-jetty-plugin</artifactId>
          <version>6.1.22</version>
        </plugin>
      </plugins>
    </build>
</project>


Gmane