Uploaded image for project: 'Codehaus Cargo'
  1. CARGO-787

ANT tasks don't detect any container if launched via <taskdef> with classpath

    Details

    • Type: Bug
    • Status: Closed (View workflow)
    • Priority: Major
    • Resolution: Fixed
    • Affects versions: 1.0.1
    • Fix versions: 1.0.2
    • Components: ANT
    • Labels:
      None

      Description

      If you define the CARGO ANT plugin like the following:

      <taskdef resource="cargo.tasks">
      <classpath>
      <pathelement location="${lib.dir}/commons-discovery-0.4.jar"/>
      <pathelement location="${lib.dir}/commons-logging-1.1.1.jar"/>
      <pathelement location="${lib.dir}/dom4j-1.4.jar"/>
      <pathelement location="${lib.dir}/jdom-1.0.jar"/>
      <pathelement location="${lib.dir}/cargo-ant-1.0.1-sr-1.jar"/>
      <pathelement location="${lib.dir}/cargo-core-uberjar-1.0.1.jar"/>
      </classpath>
      </taskdef>
      

      the CARGO ANT plugin cannot find any container. It shows messages like:

      org.codehaus.cargo.container.ContainerException: Cannot create configuration.
      There's no registered configuration for the parameters (container [id = [tomcat6x],
      type = [installed]], configuration type [standalone]). Actually there are no valid
      types registered for this configuration. Maybe you've made a mistake spelling it?
      

        Attachments

          Activity

            People

            • Assignee:
              savasalitokmen Savas Ali Tokmen (Inactive)
              Reporter:
              savasalitokmen Savas Ali Tokmen (Inactive)
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: