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/07/09 23:39:58 UTC
[jira] Created: (TIKA-462) Add Boilerpipe 1.0.4 to Maven central
and remove java.net repository from parser pom
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
Reporter: Ken Krugler
Assignee: Jukka Zitting
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.
[jira] Commented: (TIKA-462) Add Boilerpipe 1.0.4 to Maven central
and remove java.net repository from parser pom
Posted by "Ken Krugler (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TIKA-462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12928256#action_12928256 ]
Ken Krugler commented on TIKA-462:
----------------------------------
The boilerpipe 1.1.0 artifact has been released at Sonatype's repo, and I've commented on the corresponding issue. So hopefully it will be sync'd to Maven central soon, after which I can remove the GoogleCode maven repo from the tika-parsers pom.xml, and close this issue.
Note that there is still an issue with the Rome 1.0 dependency - see TIKA-543.
> 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.
[jira] Commented: (TIKA-462) Add Boilerpipe 1.0.4 to Maven central
and remove java.net repository from parser pom
Posted by "Ken Krugler (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TIKA-462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12926730#action_12926730 ]
Ken Krugler commented on TIKA-462:
----------------------------------
I created [https://issues.sonatype.org/browse/OSSRH-950] to get this jar pushed to Maven central.
> 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.
[jira] Commented: (TIKA-462) Add Boilerpipe 1.0.4 to Maven central
and remove java.net repository from parser pom
Posted by "Ken Krugler (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Resolved: (TIKA-462) Add Boilerpipe 1.0.4 to Maven central
and remove java.net repository from parser pom
Posted by "Ken Krugler (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TIKA-462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ken Krugler resolved TIKA-462.
------------------------------
Resolution: Fixed
Committed: http://svn.apache.org/viewvc?view=revision&revision=1031562
> 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.
[jira] Updated: (TIKA-462) Add Boilerpipe 1.0.4 to Maven central
and remove java.net repository from parser pom
Posted by "Chris A. Mattmann (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TIKA-462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chris A. Mattmann updated TIKA-462:
-----------------------------------
Component/s: config
documentation
packaging
- classify the component
> 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.
[jira] Assigned: (TIKA-462) Add Boilerpipe 1.0.4 to Maven central
and remove java.net repository from parser pom
Posted by "Ken Krugler (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TIKA-462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ken Krugler reassigned TIKA-462:
--------------------------------
Assignee: Ken Krugler (was: Jukka Zitting)
> 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
> 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.
[jira] Updated: (TIKA-462) Add Boilerpipe 1.0.4 to Maven central
and remove java.net repository from parser pom
Posted by "Ken Krugler (JIRA)" <ji...@apache.org>.
[ 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.