« Return to Thread: Remote Tomcat deployment via Cargo Ant Task
S. Ali Tokmen wrote:Hi
Looked into this in details and opened
https://jira.codehaus.org/browse/CARGO-962
This issue should have been fixed now. Please try with the latest
1.1.0-SNAPSHOT, which you can download from
http://bamboo.ci.codehaus.org/browse/CARGO-TRUNKM3JDK16-154/artifact
(make sure you download both the latest uberjar + ANT tasks).
Once you test, can you also report back so we close the issue?
Thank you
S. Ali Tokmen
http://ali.tokmen.com/
GSM (ch): +41 79 207 29 22 [Swisscom]
GSM (fr): +33 66 43 00 555 [Orange]
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
On 07.04.2011 19:07, S. Ali Tokmen wrote:
> Hi
>
> I believe this is because CargoTask checks for an attribute called
> refId; and when that one is null considers that the container should
> have a home.
>
> Does anyone know what refId is?
>
> As a workaround, can you please add an attribute home="nowhere" to the
> container?
>
> Thank you
>
> S. Ali Tokmen
> http://ali.tokmen.com/
>
> GSM (ch): +41 79 207 29 22 [Swisscom]
> GSM (fr): +33 66 43 00 555 [Orange]
> 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
>
>
> On 06.04.2011 22:26, Benjamin Muschko wrote:
>> 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:
>>
>> 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:
>>
>> <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>
> ---------------------------------------------------------------------
> 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
« Return to Thread: Remote Tomcat deployment via Cargo Ant Task
| Free embeddable forum powered by Nabble | Forum Help |