[CLI-298] Define CLI options via configuration file

• Type: Improvement
• Status: Open
• Priority: Minor
• Resolution: Unresolved
• Affects Version/s: 1.5.0, Nightly Builds
• Component/s: Options definition
• Labels: newbie pull-request-available ready-to-commit
• Assignee: Unassigned
• Reporter: Richard
• Created: 16/Oct/19 19:16
• Updated: 21/Oct/19 21:01

Description

Create a configuration that enables users to define CLI options via a configuration file. Such configuration would normally pre-defined and bundled inside the executable jar running the application. This would reduce the amount of code required to define command line options and introduce the ability to do a lot of the checking a user does (such as converting values to integers, files, checking if integers are above/below a certain amount, checking that files or directories do/don't exist etc.) For security purposes, at compile time calculate an MD5 for the application, if this doesn't match at runtime warn of corrupted file exception. Also add I18N since this will be driven via the user experience for exception messages.

So far I've catered for basic options that utilise strings.

Code already started with a pull request at https://github.com/zendawg/commons-cli underneath the branch named "cli-configuration".

Apologies in advance, never contributed to Apache SWF before.