[ https://issues.apache.org/jira/browse/TIKA-3293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17562934#comment-17562934 ]
Tilman Hausherr commented on TIKA-3293: --------------------------------------- This was fixed in TIKA-3529 and TIKA-3746. {code:java} String os = System.getProperty("os.name"); if (os.startsWith("Windows")) { assertEquals(-1, process.exitValue()); } else { assertEquals(255, process.exitValue()); } {code} So please tell what your "os" is. > Move most commandline options for tika-server into a config file in 2.0.0 > ------------------------------------------------------------------------- > > Key: TIKA-3293 > URL: https://issues.apache.org/jira/browse/TIKA-3293 > Project: Tika > Issue Type: Task > Reporter: Tim Allison > Priority: Major > > We now have a huge amount of commandline options for tika-server. I propose > moving them into a config file. Given that TikaConfig doesn't mind elements > that it isn't looking for, we can add this to a tika-config.xml file. > > I tried to extend TikaConfig, and it was, um, non-trivial. So, this proposal > would have tika-server and tikaconfig reading the same file twice and looking > for different elements. > > Any objections? -- This message was sent by Atlassian Jira (v8.20.10#820010)