Details
Description
The name property defined for a deployable is ignored for remote ear deployment for glassfish3. It is very similar to the CARGO-598 issue.
The plugin configuration for cargo is as it follows (it is part of an ear project):
<plugin> <groupId>org.codehaus.cargo</groupId> <artifactId>cargo-maven2-plugin</artifactId> <version>1.0.6</version> <configuration> <container> <containerId>glassfish3x</containerId> <type>remote</type> </container> <configuration> <type>runtime</type> <properties> <cargo.hostname>localhost</cargo.hostname> <cargo.glassfish.adminPort>4848</cargo.glassfish.adminPort> <cargo.remote.password>password</cargo.remote.password> <cargo.remote.username>admin</cargo.remote.username> </properties> </configuration> <deployer> <deployables> <deployable> <properties> <name>office</name> </properties> </deployable> </deployables> </deployer> </configuration> <dependencies> <dependency> <groupId>org.glassfish.deployment</groupId> <artifactId>deployment-client</artifactId> <version>3.0</version> </dependency> </dependencies> </plugin>
I have also tried:
- to define the deployable explicitly (not using the default values), but it did not help
- use the deployables in the configuration section, but it did not help
Committed revision 2880, which should fix this issue.
Can you please try with Cargo 1.1.0-SNAPSHOT? Instructions for doing so are on: http://cargo.codehaus.org/Maven2+Plugin+Installation#Maven2PluginInstallation-snapshots
Thank you