[
https://issues.jboss.org/browse/AS7-2672?page=com.atlassian.jira.plugin.s...
]
Alexey Loubyansky resolved AS7-2672.
------------------------------------
Fix Version/s: 7.1.0.CR1
Resolution: Done
I fixed it by not accepting any of the server-groups arguments (--disable is also
disallowed in this case) if --force is present. --force only replaces the content in the
repository and nothing more. This is actually how it has been, no changes in the
functional aspect, I just added the validation of the combination of the arguments.
Deploy from CLI of archive already in domain to a different server
group messaging or bug.
-------------------------------------------------------------------------------------------
Key: AS7-2672
URL:
https://issues.jboss.org/browse/AS7-2672
Project: Application Server 7
Issue Type: Feature Request
Components: CLI
Reporter: Drew Stockdreher
Assignee: Alexey Loubyansky
Labels: eap6-ux
Fix For: 7.1.0.CR1
If an archive (example.war) is deployed to a domain, and a deploy command is run to
deploy to a server group that does not currently have the archive in it, the message
indicates a successful deployment, but the archive is not added to the server group.
Steps: Create two server groups.
run a deploy command from CLI.
deploy example.war --force --server-groups=server-group-1
notice it is now deployed to all servers in server-group-1
run a deploy command to deploy the same archive to server-group-2
deploy example.war --force --server-groups=server-group-2
You get the message "'example.war' re-deployed successfully."
However, when you attempt to hit any nodes in server-group-2, the application is
not deployed.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira