Better expose entry points for pmd-cli integration#52
Conversation
- This allows consumers (ie: pmd-cli) to access the Designer version without requiring JavaFX
- All other commands allow for --debug and -D on top of --verbose and -v
- The JCommander usage is deprecated - We update debug params for compatibility with all PMD commands - We allow to call startGui directly
|
This landed in the master branch - was with intended? The work in pmd/pmd#4059 is for pmd7... The only incompatibility seems to be Wdyt? |
|
Yes, this was intended. The changes are meant to be harmless, and included deprecations / changes to flags that would leave time to people to adapt to, and by minimizing differences between master and pmd7 merge should be easier down the line. Having lost |
- this depends on pmd/pmd-designer#52 being merged into master and then master merged onto compat-7.0
DesignerVersionas a standalone equivalent ofPMDVersion. By having access to this POJO outside ofDesignerit's possible to for pmd-cli to show the designer version (through$ pmd designer --version) without requiring JavaFX to be available.DesignerStarter.startGuiso that pmd-cli can invoke it. Have it return the exit code vs performing aSystem.exiton it's own.-vand--verbose, but also through-Dand--debugfor compatibility with all other pmd commands supported in pmd-cli.