[ https://issues.apache.org/jira/browse/TIKA-2241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15827518#comment-15827518 ] Andreas Baumann commented on TIKA-2241: --------------------------------------- Opened new bug TIKA-2243 for the GrobidRESTParser issue. > DumpTikaConfigExample generates strange tika-config.xml > -------------------------------------------------------- > > Key: TIKA-2241 > URL: https://issues.apache.org/jira/browse/TIKA-2241 > Project: Tika > Issue Type: Bug > Components: example > Affects Versions: 1.14 > Environment: Apache Maven 3.2.5 > Java version: 1.8.0_112, vendor: Oracle Corporation > Archlinux: > OS name: "linux", version: "4.8.11-1-arch", arch: "amd64", family: "unix" > Reporter: Andreas Baumann > Priority: Trivial > > {code:none|borderStyle=solid} > mvn exec:java -Dexec.mainClass="org.apache.tika.example.DumpTikaConfigExample" -Dexec.arguments="--dump-static" > {code} > Tika 1.8 used to produce something like: > {code:xml|borderStyle=solid} > > > > > > > > > > > > > application/java-vm > > > audio/basic > audio/x-aiff > audio/x-wav > ... > {code} > With Tika 1.14 I get: > {code:xml|borderStyle=solid} > > > > > > > > > > > > > > > > > > > > > > ... > {code} > The following problems IMHO: > - Why are all classes in double? > - As I understood the order of the parsers matters: earliler ones > take precendence over later ones? > - Matching MIME-types are missing completely? -- This message was sent by Atlassian JIRA (v6.3.4#6332)