Make the JBoss (or WildFly deployer) not rename the deployable file name if the WAR has a jboss-web.xml with a context defined in it

Description

See: https://groups.google.com/forum/#!topic/codehaus-cargo/LLOwaQ9RSmc

We recently switched from the Wildfly plugin for Maven to Cargo's Wildfly support, and stumbled on an interesting but frustrating difference.

We have a jboss-web.xml setting the context to /foo, and a WAR artifact called foo-api.war. If we use the Maven plugin, it shows up in deployments as "foo-api.war", and is hosted on "/foo" as expected.

If we try to do the same thing with Cargo, cargo reads the jboss-web.xml and renames the war file. So it shows up in deployments as "foo.war" (and is also hosted on "/foo").

Status

Assignee

S. Ali Tokmen

Reporter

S. Ali Tokmen

Components

Fix versions

Priority

Low