[
https://issues.apache.org/jira/browse/TIKA-761?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13134140#comment-13134140
]
Ingo Renner commented on TIKA-761:
----------------------------------
bq. +1 Looks good.
thanks!
bq. As a possible improvement, as Nick noted, you could read the version number
from /META-INF/MANIFEST.MF or from
/META-INF/maven/org.apache.tika/tika-app/pom.properties so we don't need to set
up a custom properties file for this.
It seems - from what I read - these are only available after building the app,
which would be too late(?)
bq. Also, it would be cool if that information could be made available also
through the Java API in tika-core. For example the toString() method of the
Tika facade class could return something like "Apache Tika x.y", and tika-app
--version would simply output that string.
I'll give it a try.
bq. -1 for backwards compatibility reasons.
fine with me, I just had the impression that -v was more common
> Provide version number by CLI argument -V
> -----------------------------------------
>
> Key: TIKA-761
> URL: https://issues.apache.org/jira/browse/TIKA-761
> Project: Tika
> Issue Type: New Feature
> Components: cli, general
> Reporter: Ingo Renner
> Priority: Minor
> Attachments: TIKA-761.diff, TIKA-761.diff, TIKA-761.diff
>
>
> I'd like to get the Apache Tika version number through CLI argument -V or
> --version. The patch is trivial and basically finished. The only thing
> missing (because Java is not my native programming language) is the actual
> version number. Any hints where I can get that from?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
