jsvede / crucible-cli Goto Github PK

the --help option and the --action XXX --help should work differently.

--help should show the minimum requirements for using the tool.

--action XXX --help should show the help as implemented in the printHelp() method of the IAction implementation.

When users create an auth token, they should be allowed to select the file name and location of their preference. This also means that when running commands there must a flag for loading the file from the custom location. The default location and file name should continue to be valid. I.e., if a user doesn't care to use this, they should continue to be able to create an auth token to the default file name and location (currently ~/crucible-cli.tkn).

Need to find out if writing the auth token to disk represents a security risk of some kind. Need to look at the Crucible docs to see how Atlassian deals with the tokens.

Install the delta pack on the target so that the build can build for multiple platforms at once.

currently using System.out as the logging mechanism. Need to find a way to debug more efficiently with some sort of --debug flag to allow for runtime debugging. Bonus points for adding a flag for --debugOutput flag which passes in a FQ file name to which to log the debugging output.

Against 2.10.3 there needs to be a PermaIdHistory field; against 2.7.6 if that field is present it causes parsing issues. When the field isn't present, then 2.10.3 blows chunks. I am assuming there is a way to properly annotate this field so that the Jackson Mapper object is happy. Find it and apply that fix.

Current the class CreateReviewAction is a one stop shop for creating a review, adding a review and adding revisions.

These should split into three actions:

createReview
addReviewers
addChangsets

So users can add reviewers and changsets to an existing review.

the parameter --config should be optional if the user defined a file called crucible.properties in their home dir.

Need to add a few pages of document to the source repo so that user can:

• install and run an already built instance.
• install the source into Eclipse if they are not a plugin developer.
• add new IAction instances and register them to be used in the cli.

Just because the REST API returns a 204 and is overall quite silent about its success, there is no need for crucible-cli to be as laconic.

Add an appropriate message upon success.

Having a target platform for this app will allow for setting up to build to multiple platforms.