We're updating the issue view to help you get more done. 

Cargo Ant Tasks do not support any action with the remote containers

Description

Full thread on: http://old.nabble.com/Remote-Tomcat-deployment-via-Cargo-Ant-Task-to31336978.html

I was trying to deploy a WAR file using the Cargo Ant task version 1.0.6 to a
remote Tomcat server. As far as I can see from the documentation I have to
set the container type to remote and the configuration type to runtime.
However, when I run it I get the following error message:

1 2 You must specify either a [home] attribute pointing to the location where the Tomcat 6.x Remote is installed, or a nested [zipurlinstaller] element

This error message doesn't quite make sense to me because I don't want to
set the home (it sits on a different server) and I don't want to download
Tomcat from an URL (zipurlinstaller) because I already have an installation
on my server. I thought using the type remote would prevent having to choose
between home and zipurlinstaller. Am I missing a specific parameter here?

Here's my Ant code:

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 <taskdef resource="cargo.tasks"> <classpath> <pathelement location="${cargo-uberjar}"/> <pathelement location="${cargo-antjar}"/> </classpath> </taskdef> <target name="cargostart" depends="war"> <cargo containerId="tomcat6x" type="remote" action="start" wait="false"> <configuration type="runtime"> <property name="cargo.tomcat.manager.url" value="http://someserver:8080/manager"/> <property name="cargo.remote.username" value="username"/> <property name="cargo.remote.password" value="password"/> <deployable type="war" file="${mywarfile}"/> </configuration> </cargo> </target>

Status

Assignee

Savas Ali Tokmen

Reporter

Savas Ali Tokmen

Components

Fix versions

Affects versions

1.0.6

Priority

Major