Details
-
Type:
Improvement
-
Status:
Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: 1.7.2
-
Component/s: None
-
Labels:None
-
Number of attachments :
Description
It seems foreseeable that we have to get away from the outdated commons cli 1.1. This move creates a problem for this builder, because for one I think it is good to have such a builder, but for two it is a big hazzle to depend on a broken lib. Therefor the builder should be modified or maybe deprecated/replaced. It would be nice if the builder could work together with a number of command line interfaces, but if there is a new builder, then it should try not to expose the underlaying cli lib too much, allowing us to replace the lib easily. Also the builder is used for example by gant, so a simple removal is probably out of question
Activity
Guillaume Laforge
made changes -
| Field | Original Value | New Value |
|---|---|---|
| Fix Version/s | 1.7-beta-x [ 15538 ] | |
| Fix Version/s | 1.7-beta-1 [ 14014 ] |
Paul King
made changes -
| Status | Open [ 1 ] | Closed [ 6 ] |
| Fix Version/s | 1.7.2 [ 16237 ] | |
| Fix Version/s | 1.7.X [ 15538 ] | |
| Resolution | Fixed [ 1 ] |
Wondering whether we should close this. CommonsCLI is now working for us but also CLIBuilder was changed to be more alternative library friendly - i.e. there is a style of using CliBuilder that doesn't ever reference the underlying implementation, so could be used with some other underlying CLI library.