You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 29, 2022. It is now read-only.
For customers who might be installing JBoss in a non-standard location, if they provide a --scan-dirs option then it would be good to go ahead and scan any specified dirs for JBoss as part of the default facts (when we are scanning common installation paths). From a usability perspective it seems odd that scan-dirs doesn't do anything unless you are running it with a specific set of facts like --facts all.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Openning a new issue
Specify type:
Bug severity (if applicable):
Description:
For customers who might be installing JBoss in a non-standard location, if they provide a --scan-dirs option then it would be good to go ahead and scan any specified dirs for JBoss as part of the default facts (when we are scanning common installation paths). From a usability perspective it seems odd that scan-dirs doesn't do anything unless you are running it with a specific set of facts like --facts all.
The text was updated successfully, but these errors were encountered: