tomcat6x cargo:undeploy with maven2 not supported error

[jamesfenster]

Hi,

I've been using the cargo maven 2 plugin.  I was trying to get my web application undeployed from the tomcat6x container.  But, whenever I attempt to run it, it comes up with a "not supported" error.
cargo:deploy works correctly.  My only issue seems to be with cargo:undeploy.

Here's the error I get:

[INFO] [cargo:undeploy {execution: clean-undeploy}]
[INFO] ------------------------------------------------------------------------
[ERROR] FATAL ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Not supported
[INFO] ------------------------------------------------------------------------
[INFO] Trace
org.codehaus.cargo.container.ContainerException: Not supported
        at org.codehaus.cargo.container.spi.deployer.AbstractDeployer.undeploy(AbstractDeployer.java:113)
        at org.codehaus.cargo.maven2.DeployerUndeployMojo.performDeployerActionOnSingleDeployable(DeployerUndeployMojo.java:39)
        at org.codehaus.cargo.maven2.AbstractDeployerMojo.performDeployerActionOnAllDeployables(AbstractDeployerMojo.java:104)
        at org.codehaus.cargo.maven2.AbstractDeployerMojo.doExecute(AbstractDeployerMojo.java:47)
        at org.codehaus.cargo.maven2.AbstractCargoMojo.execute(AbstractCargoMojo.java:255)
        at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:483)
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:678)
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:540)
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:519)
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:371)
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:332)
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:181)
        at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:356)
        at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:137)
        at org.apache.maven.cli.MavenCli.main(MavenCli.java:356)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:597)
        at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
        at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
        at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
        at org.codehaus.classworlds.Launcher.main(Launcher.java:375)

Has anyone seen this error before?

Thanks for the help,

Matt

[Rusty Wright-2]

What's your "type"?  I can't use a type of existing because my tomcat runs as the user tomcat and so the app directory in ~tomcat/webapps is owned by tomcat, so I use a type of remote.  Here's the stuff from my pom:

            <plugin>
                <groupId>org.codehaus.cargo</groupId>
                <artifactId>cargo-maven2-plugin</artifactId>
                <version>${version.cargo}</version>

                <!-- the tomcat username and password should be in a        -->
                <!--  profile section in your ~/.m2/settings.xml file, not  -->
                <!-- here or a profile in any of your pom.xmls.             -->

                <!-- the tomcat.hostname property is in a profile down      -->
                <!-- below. same for the port.                              -->

<!--
this doesn't work because cargo can't undeploy the app when it's
running because tomcat owns the app's directory.  with the remote
setup it can since it uses the tomcat manager, which runs in tomcat.
-->

<!--
                <configuration>
                    <configuration>
                        <type>existing</type>
                        <home>/home/tomcat</home>
                    </configuration>

                    <container>
                        <containerId>tomcat6x</containerId>
                        <type>installed</type>
                        <home>/home/tomcat</home>
                    </container>

                    <deployer>
                        <type>installed</type>

                        <deployables>
                            <deployable>
                                <groupId>edu.berkeley.ist.waitlist</groupId>
                                <artifactId>waitlist-war</artifactId>

                                <type>war</type>

                                <properties>
                                    <context>waitlist</context>
                                </properties>

                                <pingURL>http://${tomcat.hostname}:${tomcat.port}/waitlist/</pingURL>
                            </deployable>
                        </deployables>
                    </deployer>
                </configuration>
-->

                <configuration>
                    <container>
                        <containerId>tomcat6x</containerId>
                        <type>remote</type>
                    </container>

                    <configuration>
                        <type>runtime</type>

                        <properties>
                            <cargo.remote.username>${tomcat.manager.username}</cargo.remote.username>
                            <cargo.remote.password>${tomcat.manager.password}</cargo.remote.password>
                            <cargo.hostname>${tomcat.hostname}</cargo.hostname>
                            <cargo.servlet.port>${tomcat.port}</cargo.servlet.port>
                        </properties>
                    </configuration>

                    <deployer>
                        <type>remote</type>

                        <deployables>
                            <deployable>
                                <groupId>edu.berkeley.ist.waitlist</groupId>
                                <artifactId>waitlist-war</artifactId>

                                <type>war</type>

                                <properties>
                                    <context>waitlist</context>
                                </properties>

                                <pingURL>http://${tomcat.hostname}:${tomcat.port}/waitlist/</pingURL>
                            </deployable>
                        </deployables>
                    </deployer>
                </configuration>
            </plugin>


jamesfenster wrote:

> Hi,
>
> I've been using the cargo maven 2 plugin.  I was trying to get my web
> application undeployed from the tomcat6x container.  But, whenever I attempt
> to run it, it comes up with a "not supported" error.
> cargo:deploy works correctly.  My only issue seems to be with
> cargo:undeploy.
>
> Here's the error I get:
>
> [INFO] [cargo:undeploy {execution: clean-undeploy}]
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] FATAL ERROR
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Not supported
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Trace
> org.codehaus.cargo.container.ContainerException: Not supported
>         at
> org.codehaus.cargo.container.spi.deployer.AbstractDeployer.undeploy(AbstractDeployer.java:113)
>         at
> org.codehaus.cargo.maven2.DeployerUndeployMojo.performDeployerActionOnSingleDeployable(DeployerUndeployMojo.java:39)
>         at
> org.codehaus.cargo.maven2.AbstractDeployerMojo.performDeployerActionOnAllDeployables(AbstractDeployerMojo.java:104)
>         at
> org.codehaus.cargo.maven2.AbstractDeployerMojo.doExecute(AbstractDeployerMojo.java:47)
>         at
> org.codehaus.cargo.maven2.AbstractCargoMojo.execute(AbstractCargoMojo.java:255)
>         at
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:483)
>         at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:678)
>         at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:540)
>         at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:519)
>         at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:371)
>         at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:332)
>         at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:181)
>         at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:356)
>         at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:137)
>         at org.apache.maven.cli.MavenCli.main(MavenCli.java:356)
>         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>         at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>         at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>         at java.lang.reflect.Method.invoke(Method.java:597)
>         at
> org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
>         at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
>         at
> org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
>         at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
>
> Has anyone seen this error before?
>
> Thanks for the help,
>
> Matt

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email