[
https://issues.jboss.org/browse/WFCORE-328?page=com.atlassian.jira.plugin...
]
ehsavoie Hugonnet commented on WFCORE-328:
------------------------------------------
Now you can do this using the new attachment command from the CLI:
{quote}[standalone@localhost:9990 /] attachment display
--operation=/deployment=kitchensink.ear:read-content(path=META-INF/MANIFEST.MF)
ATTACHMENT e11aee53-4c7c-4bf8-960d-65a9890b05ff:
Manifest-Version: 1.0
Archiver-Version: Plexus Archiver
Built-By: ehsavoie
Created-By: Apache Maven 3.3.9
Build-Jdk: 1.8.0_101{quote}
Provide deployment manifest information via the CLI
---------------------------------------------------
Key: WFCORE-328
URL:
https://issues.jboss.org/browse/WFCORE-328
Project: WildFly Core
Issue Type: Feature Request
Components: CLI, Domain Management
Reporter: Brian Stansberry
Assignee: ehsavoie Hugonnet
Fix For: 3.0.0.Alpha8
We've gotten a user request for providing the contents of a deployment's
MANIFEST.MF via the CLI.
The request is to include an option to get the manifest info for a single deployment, and
also the info for all deployments.
This task needs to be evaluated in relationship to the larger request to provide read
(and possibly in some cases write) access to all files within a deployment. The manifest
is essentially just one file with a standard location.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)