[
https://issues.apache.org/jira/browse/TIKA-462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12928257#action_12928257
]
Ken Krugler commented on TIKA-462:
----------------------------------
See
https://docs.sonatype.org/display/Repository/Sonatype+OSS+Maven+Repository+Usage+Guide
for details on how to get something into Sonatype, and then on to Maven
central.
Also note that if you use Maven 2.2.0, and are trying to use the "deploy with
gpg" approach, you'll get invalid checksums. You need to upgrade to Maven 2.2.1.
> 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
>
>
> [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.
