Bug 1299182 - [GSS] Document *.cli deployment deploy.scr / undeploy.scr
Summary: [GSS] Document *.cli deployment deploy.scr / undeploy.scr
Keywords:
Status: CLOSED EOL
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Documentation
Version: 6.4.6
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: eap-docs
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-01-17 03:54 UTC by Brad Maxwell
Modified: 2020-01-02 15:16 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-08-19 12:44:08 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker JBEAP-5080 0 Major New Document CLI deployment archive usage (CLI guide) 2020-01-02 15:16:54 UTC
Red Hat Knowledge Base (Solution) 1141553 0 None None None 2016-01-17 03:54:23 UTC

Description Brad Maxwell 2016-01-17 03:54:23 UTC
Description of problem:

There is a feature where a cli deployment can be deployed via the CLI which can include deploy.scr and undeploy.scr which can contain CLI commands to run during deployment.

From what I've seen it must be deployed through the CLI, copying into the deployments directory does not work.

test.cli
 - deploy.scr
 - undeploy.scr
 - servlet-annotations.war

deploy.scr
--------------------
/system-property=test:add(value=success)
deploy servlet-annotations.war

Deploying such as this, shows that the system property gets set and the servlet-annotations.war when deployed will read the system property showing that test=success

jboss-cli.sh -c
deploy test.cli

Document URL: 

Section Number and Name: 

Describe the issue: 

Suggestions for improvement: 

Additional information:


Note You need to log in before you can comment on or make changes to this bug.