I've pushed simple fix for TIKA-2056 which broke build in presense of
`ffmpeg` or `exiftool`. I'm unaware how much of downstream users actually
use `ForkParser` but issue in JIRA wasn't really hot, so my +1 for rc1.
Thanks, Chris.

[x] +1 Release this package as Apache Tika 1.14
[ ] -1 Do not release this package because..

пн, 31 окт. 2016 г. в 19:05, Mattmann, Chris A (3010) <
[email protected]>:

> I’m happy to roll with this RC – it definitely has to do with something
> that exiftool
> installs or with exiftool itself. Recommend checking out the issue that we
> filed that
> Tim linked earlier.
>
> Konstantin, Tim, I will finish off the release this week if there are no
> further objections.
> I think we have enough +1s to move forward. I’ll finish the RC on Friday
> if there are
> no further comments.
>
> Thanks,
> Chris
>
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> Chris Mattmann, Ph.D.
> Principal Data Scientist, Engineering Administrative Office (3010)
> Manager, Open Source Projects Formulation and Development Office (8212)
> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
> Office: 180-503E, Mailstop: 180-502
> Email: [email protected]
> WWW:  http://sunset.usc.edu/~mattmann/
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> Director, Information Retrieval and Data Science Group (IRDS)
> Adjunct Associate Professor, Computer Science Department
> University of Southern California, Los Angeles, CA 90089 USA
> WWW: http://irds.usc.edu/
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
>
> On 10/31/16, 9:02 AM, "Allison, Timothy B." <[email protected]> wrote:
>
>     Aside from the PGP key issues, do we need more time to understand the
> serializable issues with AutoDetectParser?  Or, are we good to go?
>
>     -----Original Message-----
>     From: Konstantin Gribov [mailto:[email protected]]
>     Sent: Monday, October 24, 2016 12:42 PM
>     To: [email protected]
>     Subject: Re: [VOTE] Apache Tika 1.14 Release Candidate #1
>
>     Chris,
>
>     you have new PGP key which is not present your account in [1]. Could
> you please update it there? Also, `KEYS` file in `tika-1.14-src.zip`
> contains only your old PGP key.
>
>     SHA-1 and MD5 digests are fine, `tika-server` and `tika-app` work fine
> on Arch Linux, OpenJDK 8u112 with and without Tesseract.
>
>     Build (`mvn clean package verify`) fails same way as Julien Nioche and
> Dave mentioned on Arch Linux with or without tesseract. I have no exiftool,
> so I'll try to investigate what else make `AutoDetectParser`
> non-serializable.
>     I hope, I'll have a bit time this evening for this.
>
>     Also, one test fails `testParserHandlingOfNonSerializable` because
> exception message was `Unable to serialize [AutoDetectParser] to pass to
> the Fork...` instead of `Unable to serialize [ParseContext] to pass to the
> Fork...`. But it seems the same issue as above.
>
>     Both issues aren't strict blockers to me but I'd ask you to increase
> voting time to dig into issue with non-serializable `AutoDetectParser` if
> you don't mind.
>
>     [1]: https://people.apache.org/keys/committer/mattmann.asc
>
>     пн, 24 окт. 2016 г. в 16:15, David Meikle <[email protected]>:
>
>     Hello,
>
>     I am getting the same as Julien without exiftool installed on my Mac.
>     Everything passes on Windows 10 and Ubuntu.
>
>     Will have a dig and see what I find.
>
>     Cheers,
>     Dave
>
>     > On 20 Oct 2016, at 13:34, Julien Nioche
>     > <[email protected]>
>     wrote:
>     >
>     > Hi
>     >
>     > Am getting the following when running 'mvn clean package', have I
>     forgotten
>     > something obvious?
>     >
>     > Julien
>     >
>     > *Failed tests: *
>     > *  ForkParserIntegrationTest.testParserHandlingOfNonSerializable:210
>     > expected:<Unable to serialize [ParseContext] to pass to the Fork...>
>     > but was:<Unable to serialize [AutoDetectParser] to pass to the
>     > Fork...>* *Tests in error: *
>     > *
>     >
>
> ForkParserIntegrationTest.testAttachingADebuggerOnTheForkedParserShouldWork:234
>     > » Tika*
>     > *  ForkParserIntegrationTest.testForkedPDFParsing:257 » Tika Unable
> to
>     > serialize ...*
>     > *  ForkParserIntegrationTest.testForkedTextParsing:66 » Tika Unable
> to
>     > serialize ...*
>     >
>     > *Tests run: 755, Failures: 1, Errors: 3, Skipped: 17*
>     >
>     > *[INFO]
>     >
> ----------------------------------------------------------------------
>     > --*
>     > *[INFO] Reactor Summary:*
>     > *[INFO] *
>     > *[INFO] Apache Tika parent ................................ SUCCESS
>     > [4.368s]*
>     > *[INFO] Apache Tika core .................................. SUCCESS
>     > [16.487s]*
>     > *[INFO] Apache Tika parsers ............................... FAILURE
>     > [4:54.631s]*
>     >
>     >
>     >
>     > On 19 October 2016 at 19:48, Chris Mattmann <[email protected]>
> wrote:
>     >
>     >> Hi Folks,
>     >>
>     >> A first candidate for the Tika 1.14 release is available at:
>     >>
>     >>  https://dist.apache.org/repos/dist/dev/tika/
>     >>
>     >> The release candidate is a zip archive of the sources in:
>     >>
>     >> https://git-wip-us.apache.org/repos/asf?p=tika.git;a=tree;hb=
>     >> 687d7706c9778e4f49f2834a07e5a9d99b23042b
>     >>
>     >> The SHA1 checksum of the archive is:
>     >> ad9152392ffe6b620c8102ab538df0579b36c520
>     >>
>     >> In addition, a staged maven repository is available here:
>     >>
>     >>
> https://repository.apache.org/content/repositories/orgapachetika-1020
>     >> /
>     >>
>     >> Please vote on releasing this package as Apache Tika 1.14.
>     >> The vote is open for the next 72 hours and passes if a majority of
> at
>     >> least three +1 Tika PMC votes are cast.
>     >>
>     >> [ ] +1 Release this package as Apache Tika 1.14 [ ] -1 Do not
> release
>     >> this package because..
>     >>
>     >> Cheers,
>     >> Chris
>     >>
>     >> P.S. Of course here is my +1.
>     >>
>     >>
>     >>
>     >>
>     >>
>     >>
>     >
>     >
>     > --
>     >
>     > *Open Source Solutions for Text Engineering*
>     >
>     > http://www.digitalpebble.com
>     > http://digitalpebble.blogspot.com/
>     > #digitalpebble <http://twitter.com/digitalpebble>
>
>     --
>
>     Best regards,
>     Konstantin Gribov
>
>
> --

Best regards,
Konstantin Gribov

Reply via email to