[
https://issues.jboss.org/browse/AS7-4385?page=com.atlassian.jira.plugin.s...
]
Alexey Loubyansky resolved AS7-4385.
------------------------------------
Fix Version/s: 7.2.0.Alpha1
Resolution: Done
Done. The deploy command now has optional --unmanaged argument which will indicate how the
content should be deployed.
Add support for fs-archive and fs-exploded deployments to the CLI
deploy command
--------------------------------------------------------------------------------
Key: AS7-4385
URL:
https://issues.jboss.org/browse/AS7-4385
Project: Application Server 7
Issue Type: Feature Request
Components: CLI
Reporter: Brian Stansberry
Assignee: Alexey Loubyansky
Fix For: 7.2.0.Alpha1
The as supports "unmanaged" deployment content via the <fs-archive> and
<fs-exploded> child elements of the deployment element. The CLI should make it
possible to take advantage of this without requiring a low level command. I haven't
looked into it carefully, but I think it could be a simple boolean param to the deploy
command. If "true", check whether the file specified by file_path is a
directory; if yes, use fs-exploded, else use fs-archive.
--
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