[
https://issues.apache.org/jira/browse/TIKA-1653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14577293#comment-14577293
]
Hudson commented on TIKA-1653:
------------------------------
SUCCESS: Integrated in tika-trunk-jdk1.7 #740 (See
[https://builds.apache.org/job/tika-trunk-jdk1.7/740/])
TIKA-1653 Re-do the XML parsing in the Tika Config, so that a parser tag with
another inside it doesn't get accidently duplicated at the top level (nick:
http://svn.apache.org/viewvc/tika/trunk/?view=rev&rev=1684199)
* /tika/trunk/tika-core/src/main/java/org/apache/tika/config/TikaConfig.java
* /tika/trunk/tika-core/src/test/java/org/apache/tika/config/TikaConfigTest.java
*
/tika/trunk/tika-core/src/test/resources/org/apache/tika/config/TIKA-1653-norepeat.xml
*
/tika/trunk/tika-parsers/src/main/java/org/apache/tika/parser/ctakes/CTAKESParser.java
> Tika config xml shouldn't read nested parser definitions as top level
> ---------------------------------------------------------------------
>
> Key: TIKA-1653
> URL: https://issues.apache.org/jira/browse/TIKA-1653
> Project: Tika
> Issue Type: Bug
> Components: config
> Affects Versions: 1.9
> Reporter: Nick Burch
> Fix For: 1.10
>
>
> Spotted while looking at TIKA-1642, if you have some Tika config xml like:
> {code}
> <properties>
> <parsers>
> <parser class="org.apache.tika.parser.ctakes.CTAKESParser">
> <parser class="org.apache.tika.parser.DefaultParser"/>
> </parser>
> </parsers>
> </properties>
> {code}
> Then because of the way that TikaConfig is fetching the elements, it will
> process the DefaultParser once as a child of CTakes, then a second time at
> the top level
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
