[
https://issues.apache.org/jira/browse/TIKA-747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13204630#comment-13204630
]
Nick Burch commented on TIKA-747:
---------------------------------
Getting the central sync to work turned out to be much more painful than
expected, not least owing to bugs in both Nexus and the SKS KeyServer, but at
last the 0.1 release has made it!
I've enabled the dependency to the Vorbis Java Tika Plugin in r1242387, which
pulls in the Tika plugin and dependencies. I've also added an integration test
that checks it all ones
The only remaining issue is with tika-app. Unfortunately, the current inlining
setup takes the first occurrence of a file, and ignores subsequent ones. This
means that the first parsers service file is taken, the Tika one, and the
Vorbis Parser one is ignored.
Wel'll need someone who knows how that maven plugin works to fix this, by
having the service files appended together, rather than using the "first one
wins" approach which is ignoring the additional files.
> Ogg Vorbis and FLAC Parsers
> ---------------------------
>
> Key: TIKA-747
> URL: https://issues.apache.org/jira/browse/TIKA-747
> Project: Tika
> Issue Type: Improvement
> Components: parser
> Affects Versions: 0.10
> Reporter: Nick Burch
> Assignee: Nick Burch
> Priority: Minor
> Fix For: 1.1
>
>
> As mentioned on the list a few weeks back, I've now finished getting an Ogg
> Vorbis and FLAC parser working. The code is available at
> https://github.com/Gagravarr/VorbisJava
> As I see it, there are three options for getting it into Tika:
> * Roll a release of the whole project from GitHub, upload jars to Maven
> Central, and add a parser pom dependency
> * Bring the parser code over to Tika, and release (+post to Central) just the
> core jar
> * Bring the whole lot over to Apache (maybe to Tika, maybe elsewhere?)
> This issue is to track the plan, and the inclusion of the parsers into Tika
> one way or another
--
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
