Cargo

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

Details

  • Type: New Feature New Feature
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 1.0.6
  • Fix Version/s: 1.1.0
  • Component/s: Ant
  • Labels:
    None
  • Complexity:
    Intermediate
  • Number of attachments :
    0

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:

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>

Issue Links

is related to

New Feature - A new feature of the product, which has yet to be developed. CARGO-128 Add support for Deployers

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Savas Ali Tokmen added a comment -

Committed revision 2850.

Show
Savas Ali Tokmen added a comment - Committed revision 2850.
Hide
Permalink
Savas Ali Tokmen added a comment -

Waiting for response on the ML to close.

Show
Savas Ali Tokmen added a comment - Waiting for response on the ML to close.
Hide
Permalink
Anders Hammar added a comment - - edited

I believe the (auto-generated) docs need to be updated as well to reflect the fact that remote deployment is now supported.

Show
Anders Hammar added a comment - - edited I believe the (auto-generated) docs need to be updated as well to reflect the fact that remote deployment is now supported.
Hide
Permalink
Savas Ali Tokmen added a comment -

OK, so this is an entirely new feature.

Note that our documentation is unconsistent for this: http://cargo.codehaus.org/Runtime+Configuration states that ANT tasks should have remote deployment; but this is untrue.

Show
Savas Ali Tokmen added a comment - OK, so this is an entirely new feature. Note that our documentation is unconsistent for this: http://cargo.codehaus.org/Runtime+Configuration states that ANT tasks should have remote deployment; but this is untrue.
Hide
Permalink
Savas Ali Tokmen added a comment -

Committed revision 2851. This issue should have been fixed now, the supported actions are deploy, undeploy and redeploy.

Please try with the latest 1.1.0-SNAPSHOT, which you can download from http://bamboo.ci.codehaus.org/browse/CARGO-TRUNKM3JDK16-155/artifact (make sure you download both the latest uberjar + ANT tasks).

Also updated http://cargo.codehaus.org/Runtime+Configuration

Show
Savas Ali Tokmen added a comment - Committed revision 2851. This issue should have been fixed now, the supported actions are deploy, undeploy and redeploy. Please try with the latest 1.1.0-SNAPSHOT, which you can download from http://bamboo.ci.codehaus.org/browse/CARGO-TRUNKM3JDK16-155/artifact (make sure you download both the latest uberjar + ANT tasks). Also updated http://cargo.codehaus.org/Runtime+Configuration
Hide
Permalink
Savas Ali Tokmen added a comment -

The user has reported: Awesome, works like a charm. Closing issue

Show
Savas Ali Tokmen added a comment - The user has reported: Awesome, works like a charm. Closing issue
Hide
Permalink
Anders Hammar added a comment -

I'm reopening as I believe that the auto-generating doc code is not updated to reflect this. It has to be updated as well.

More specifically, ConfluenceContainerDocumentationGenerator seems to have 'no' hard-coded for this. For example, if you look at
http://cargo.codehaus.org/JBoss+5.x
you'll see that it states that the remote deployer is not support with Ant (for this specific container).

Show
Anders Hammar added a comment - I'm reopening as I believe that the auto-generating doc code is not updated to reflect this. It has to be updated as well. More specifically, ConfluenceContainerDocumentationGenerator seems to have 'no' hard-coded for this. For example, if you look at http://cargo.codehaus.org/JBoss+5.x you'll see that it states that the remote deployer is not support with Ant (for this specific container).
Hide
Permalink
Anders Hammar added a comment -

My bad. I now see you fixed this as well. Closing.

Show
Anders Hammar added a comment - My bad. I now see you fixed this as well. Closing.

People

  • Assignee:
    Savas Ali Tokmen
    Reporter:
    Savas Ali Tokmen
Vote (1)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: