[
https://issues.jboss.org/browse/AS7-4220?page=com.atlassian.jira.plugin.s...
]
Alexey Loubyansky moved JBPAPP-8488 to AS7-4220:
------------------------------------------------
Project: Application Server 7 (was: JBoss Enterprise Application Platform)
Key: AS7-4220 (was: JBPAPP-8488)
Workflow: GIT Pull Request workflow (was: jira)
Affects Version/s: 7.1.1.Final
(was: EAP 6.0.0 ER 3_Beta1)
Security: (was: JBoss Internal)
Docs QE Status: (was: NEW)
CLONE - Typo in CLI for the read-resource-description for the
deployment scanner subsystem
------------------------------------------------------------------------------------------
Key: AS7-4220
URL:
https://issues.jboss.org/browse/AS7-4220
Project: Application Server 7
Issue Type: Bug
Affects Versions: 7.1.1.Final
Reporter: Dave Ryan
Assignee: Alexey Loubyansky
Priority: Minor
Potential typo in a description for the auto-deploy-exploded attribute of the deployment
scanner. Says "zipped" where it should say "exploded". I suspect the
cause is just copying and pasting the auto-deploy-zipped text but missing the
"exploded" change.
I've actually rewritten most of these descriptions in my documentation of the
attributes for a reference topic. If you want to check those as potential updates, I can
paste them in. I do imply assumed knowledge of boolean values to keep the sentences short.
For example, I rewrote the auto-deployed-exploded as:
"Allows the automatic deployment of exploded content without requiring a .dodeploy
marker file. Recommended for only basic development scenarios to prevent exploded
application deployment from occuring during changes by the developer or operating
system."
Was:
"Controls whether zipped deployment content should be automatically deployed by the
scanner without requiring the user to add a .dodeploy marker file. Setting this to
'true' is not recommended for anything but basic development scenarios, as there
is no way to ensure that deployment will not occur in the middle of changes to the
content."
--
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