Skip to content

Conversation

jrhe
Copy link

@jrhe jrhe commented Jun 20, 2014

When parsing some emails in a PST file I get the error "Unknown message type: IPM.Note" preventing them from being parsed. This is because of an extra null byte at the end of the message class string.
This has been fixed in version 0.8.1 of java-libpst so a version bump is all that is required.
rjohnsondev/java-libpst#14

@Gagravarr
Copy link
Contributor

Is Java libpst 0.8.1 available in maven central? Only I'm not able to see it - http://repo1.maven.org/maven2/com/pff/java-libpst/ only shows 0.7

(We can only accept dependencies that are in Maven Central)

@jrhe
Copy link
Author

jrhe commented Jun 20, 2014

Why do you only accept deps that in in Maven Central? No its not. I guess I need to pester the author of libpst to publish it?

@Gagravarr
Copy link
Contributor

It is ASF policy that releases that are pushed to Maven Central (which ours are) must not depend on external repos, and may only depend on other resources in Central. There's quite a few blog posts explaining the rationale for this if you google

If possible, ask the libpst author to upload to central via the sonatype oss repo - https://docs.sonatype.org/display/Repository/Sonatype+OSS+Maven+Repository+Usage+Guide . First release can be a faff, but once setup it's generally only a few mins extra work (or at least that's what I've found!). If they aren't willing/able, it's possible for someone else to push it for them, see https://docs.sonatype.org/display/Repository/Uploading+3rd-party+Artifacts+to+The+Central+Repository

@jrhe
Copy link
Author

jrhe commented Jun 20, 2014

Cheers for the help. The java packaging situation has changed a lot since used it!

Is there anyway I can build tika with java-libpst 0.8.1 in the meanwhile?

@Gagravarr
Copy link
Contributor

I've added some stuff on the maven central requirements to the contributing page http://tika.apache.org/contribute.html

As for building Tika with libpst 0.8.1, if it's in a non-standard repo, you can always add that to your tika parsers pom, then bump the dependency and build locally. If not, you'll need to build a pom for it, install it in a repo or your local m2 repo cache, then bump the tika parsers dependency

@asfgit asfgit closed this in 598966a Jun 24, 2014
tballison pushed a commit to tballison/tika that referenced this pull request Feb 26, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants