[jboss-jira] [JBoss JIRA] (WFLY-4177) Deployment info should not accept wildcard as server-group parameter
Filippe Spolti (JIRA)
issues at jboss.org
Thu Dec 11 21:21:29 EST 2014
[ https://issues.jboss.org/browse/WFLY-4177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Filippe Spolti updated WFLY-4177:
---------------------------------
Git Pull Request: https://github.com/wildfly/wildfly-core/pull/396
> Deployment info should not accept wildcard as server-group parameter
> --------------------------------------------------------------------
>
> Key: WFLY-4177
> URL: https://issues.jboss.org/browse/WFLY-4177
> Project: WildFly
> Issue Type: Enhancement
> Components: CLI
> Affects Versions: 9.0.0.Alpha1
> Environment: All environments.
> Reporter: Filippe Spolti
> Assignee: Filippe Spolti
> Priority: Optional
> Labels: core
> Fix For: No Release
>
> Original Estimate: 2 days
> Remaining Estimate: 2 days
>
> Actually the deployment-info in a domain mode accepts the wildcard *, but when the * is given the CLI lists only the last server-group in the list, not all. The help says:
> - single server group with a state report about each deployment in the
> domain with regard to the selected server group.
> In this case, the --server-group argument is required and its value
> must be a specific server group name, not a wildcard expression.
> The output of the command is a table with headers NAME, RUNTIME-NAME and STATE.
> Ex:
> [domain at localhost:9990 /] deployment-info --name=test.war --server-group=*
> NAME RUNTIME-NAME STATE
> test.war test.war not added
> After the change:
> [domain at localhost:9990 /] deployment-info --name=test.war --server-group=*
> Wildcards are note permited here, please give a valid server-group name.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
More information about the jboss-jira
mailing list