-
Story
-
Resolution: Done
-
Major
-
None
-
None
Feedback from Marc Zottner from most recent RHAMT Training Lab
https://docs.google.com/document/d/1YrzZ2RjiqZqkekNR5vdgi1Zwd-U89Nh3LoOAVa86y6s/edit?ts=59db88f8#
What can be done to make the CLI more resilient (no crash/stack trace) for wrong or missing parameters?
The specific example that Marc has reported
"$ rhamt-cli --output "
may already have been resolved
https://issues.jboss.org/browse/WINDUP-1702
https://github.com/windup/windup-distribution/issues/47
- If incorrect parameters are supplied can a more informative, user friendly message be returned.
- Is there a -help option for the CLI to describe what parameters are required
- It takes far too long to to display the tech list / target / source technologies
- is related to
-
WINDUP-1758 CLI: listTags option doesn't take into account user rules
- Closed
- relates to
-
WINDUP-1702 IndexOutOfBoundsException if --output is specified with no arguments
- Dev Complete
-
WINDUP-1768 It takes far too long to to display the tech list / target / source technologies
- Dev Complete
-
WINDUP-1730 CLI handling of wrong options
- MODIFIED
-
WINDUP-1767 CLI to describe what parameters are required
- Closed