Closed shiruba closed 11 years ago
Is this issue be fixed? Otherwise i´ll have to make some workaround.
As long as I saw, some work will have to be done on jboss-as-controller-client (now wildfly...) to accept the runtimeName when it's building the deploy plan. And then add this parameter to jboss-as-maven-plugin.
The interfaces that need to accept runtimeName:
Standalone
Domain
Moving to JIRA https://issues.jboss.org/browse/JBASMP-53
The JBoss CLI provides a parameter called --runtime-name, which lets you set an additional runtime name for an deployment (complementing the already supported --name parameter).
It would be nice if the JBoss Maven plugin could add another configuration parameter for this.