Hi,

Ok. My issue was that I could not build while the PDFBox Jenkins has
succesfull builds. So I was wondering why. But I run the tests in Eclipse,
which ignores the test exclusions in the pom.xml. Now it is clear for me.

Cornlelis Hoeflake


2014-09-15 20:44 GMT+02:00 John Hewson <j...@jahewson.com>:

> Yep, this test was failing back in January when I first encountered it. It
> uses some external certificate files, which could be the problem, but I
> really don’t know anything about it.
>
> -- John
>
> On 13 Sep 2014, at 08:32, Tilman Hausherr <thaush...@t-online.de> wrote:
>
> > I had a look:
> > - yes it fails in 2.0 but not in 1.8
> > - it still fails with the correction I mentioned is done (can't match
> the recipient)
> > - the test was removed long ago which is why the builds don't fail
> > - that part was written by one Benoit Guillon, who has moved on
> >
> > I don't know why the test was removed. John mentioned this before in
> PDFBOX-1825. I don't know enough about bc to understand what's wrong.
> >
> > Tilman
> >
> > Am 12.09.2014 um 10:49 schrieb Cornelis Hoeflake:
> >> Hi,
> >>
> >> I get exceptions when running the
> org.apache.pdfbox.encryption.TestPublicKeyEncryption tests. It is saying
> that the document is alread closed when calling the save method in reload.
> >>
> >> I get failures when running org.apache.pdfbox.util.TestPDFToImage,
> >>
> >> Is there something wrong with my test setup or are there more
> developers having these errors/failures?
> >>
> >> Met vriendelijke groet,
> >>
> >> Cornelis Hoeflake
> >>
> >> *Postex |  post opnieuw uitgevonden
> >> *[t]  088 07 07 400
> >> [m] 06 18684806
> >> [w] www.postex.com <http://www.postex.com/>
> >>
> >> Postex Nederland B.V. - Postbus 70466 - 1007 KL  Amsterdam
> >>
> >> **
> >>
> >>
> >> The information in this message is confidential and may be legally
> privileged.
> >> It is intended solely for the addressee. Access to this message by
> anyone else is unauthorized.
> >> If you are not the intended recipient, any disclosure, copying, or
> distribution of the message,
> >> or any action or omission taken by you in reliance on it, is prohibited
> and may be unlawful.
> >> Please immediately contact the sender if you have received this message
> in error.
>
>

Reply via email to