You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tika.apache.org by "Ken Krugler (JIRA)" <ji...@apache.org> on 2010/11/05 14:34:42 UTC
[jira] Updated: (TIKA-462) Add Boilerpipe 1.0.4 to Maven central
and remove java.net repository from parser pom
[ https://issues.apache.org/jira/browse/TIKA-462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ken Krugler updated TIKA-462:
-----------------------------
Attachment: TIKA-462.patch
Remove GoogleCode repository, since boilerpipe-1.1.0 is now in Maven Central repo.
> Add Boilerpipe 1.0.4 to Maven central and remove java.net repository from parser pom
> ------------------------------------------------------------------------------------
>
> Key: TIKA-462
> URL: https://issues.apache.org/jira/browse/TIKA-462
> Project: Tika
> Issue Type: Bug
> Components: config, documentation, packaging
> Reporter: Ken Krugler
> Assignee: Ken Krugler
> Fix For: 0.8
>
> Attachments: TIKA-462.patch
>
>
> [TIKA-420] adds the BoilerpipeContentHandler to Tika. This requires the boilerpipe 1.0.4 jar, which in turn means the tika-parsers pom has to reference the java.net Maven repo, which is where this jar is currently located.
> But this means Tika can no longer be pushed to the Maven central repo, as no external dependencies are allowed.
> So prior to the 0.8 release, we should do a one-shot upload of boilerpipe 1.0.4 to Sonatype, which in turn will sync it to Maven central.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.