[
https://issues.jboss.org/browse/JBASMP-53?page=com.atlassian.jira.plugin....
]
James Perkins commented on JBASMP-53:
-------------------------------------
This is the definition for the `--runtime-name`. Does this fit what you'd need?
{quote}
optional, the runtime name for the deployment. This will
form the basis for such things as default Java EE
application and module names. This would typically be the
same as --name, and if not specified the value used for
--name will be used. In some cases users may wish to have
two deployments with the same 'runtime-name' (e.g. two
versions of "example.war") both available in the management
configuration, in which case the deployments would need to
have distinct 'name' values but would have the same
'runtime-name'. Within an individual server, only one
deployment with a given 'runtime-name' can deployed.
However, multiple deployments with the same 'runtime-name'
can exist in the configuration, so long as only one is
enabled.
{quote}
Support --runtime-name for deployment on server groups
------------------------------------------------------
Key: JBASMP-53
URL:
https://issues.jboss.org/browse/JBASMP-53
Project: JBoss AS Maven Plugins
Issue Type: Enhancement
Components: wildfly
Reporter: James Perkins
Assignee: James Perkins
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.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)