[
https://issues.apache.org/jira/browse/PDFBOX-2602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17255594#comment-17255594
]
Maruan Sahyoun commented on PDFBOX-2602:
----------------------------------------
{quote}
PDFDebugger has also command line options...
{quote}
... and has been switched to picocli too.
{quote}
I don't understand what you mean with "interactive shell".
{quote}
Idea is - to further out - call the pdfbox app and if nothing has been
specified switch into an interactive mode to issue commands.
initially I'd like it to play nice in shell scripts only for the 3.0.0 release.
I understand why you'd like to keep PDFDebugger wrapped into PDFBox app OTOH it
will not be integrated into shell scripts, no input/output piping... - and
looking into generating a native image (not now) - I think PDFDebugger and the
other tools shall exist in separate executables
> Enhance command line tools
> --------------------------
>
> Key: PDFBOX-2602
> URL: https://issues.apache.org/jira/browse/PDFBOX-2602
> Project: PDFBox
> Issue Type: Bug
> Components: Utilities
> Affects Versions: 1.8.8, 2.0.0
> Reporter: Maruan Sahyoun
> Assignee: Maruan Sahyoun
> Priority: Minor
> Fix For: 3.0.0 PDFBox
>
>
> The command line tools shall be enhanced to have the same behavior across all
> tools.
> From the discussion on the dev mailing list
> - add an -h option to print the usage
> - print the usage to System.err and use an exit code of 1 if there was an
> invalid command line parameter
> - print messages on exceptions to System.err
> - rethrow the exception so java can handle it if it will terminate afterwards
> anyway
> - use an exit code of 1if rethrowing doesn't make sense
> Additional input:
> https://clig.dev/
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
