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

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

Description

If you define the CARGO ANT plugin like the following:

1 2 3 4 5 6 7 8 9 10 <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:

1 2 3 4 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?

Status

Assignee

Savas Ali Tokmen

Reporter

Savas Ali Tokmen

Components

Fix versions

Affects versions

1.0.1

Priority

Major