Mailing-List: contact users-help@pdfbox.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@pdfbox.apache.org
Received-SPF: pass (athena.apache.org: local policy)
Message-ID: <53A11DBE.7040604@t-online.de>
Date: Wed, 18 Jun 2014 07:03:58 +0200
From: Tilman Hausherr <THausherr@t-online.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64;
 rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: users@pdfbox.apache.org
Subject: Re: Disabling TestImageIOUtils
References: <5363C751.7010508@lehmi.de> <536AF755.4050803@cora.nwra.com>
 <1185585950.798614.1400234020855.open-xchange@patina.store>
 <53A116C3.4000605@cora.nwra.com>
In-Reply-To: <53A116C3.4000605@cora.nwra.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit

Am 18.06.2014 06:34, schrieb Orion Poplawski:
> On 05/16/2014 03:53 AM, Andreas Lehmkühler wrote:
>> Hi,
>>
>>
>>> Orion Poplawski <orion@cora.nwra.com> hat am 8. Mai 2014 um 05:17 geschrieben:
>>>
>>>
>>> On 05/02/2014 10:26 AM, Andreas Lehmkuehler wrote:
>>>> The Apache PDFBox community is pleased to announce the release of
>>>> Apache PDFBox version 1.8.5. The release is available for download at:
>>>>
>>>>      http://pdfbox.apache.org/downloads.html
>>> This release presents something of a challenge for the Fedora package.
>>> First off I will need to disable access to
>>> com.levigo.jbig2:levigo-jbig2-imageio and possibly
>>> net.java.dev.jai-imageio:jai-imageio-core-standalone in pdfbox.
>>>
>>>    But then I get test failures:
>>>
>>> Tests run: 139, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 9.121
>>> sec <<< FAILURE! - in org.apache.pdfbox.TestAll
>>> testRenderImage(org.apache.pdfbox.util.TestImageIOUtils)  Time elapsed:
>>> 1.238 sec  <<< FAILURE!
>>> junit.framework.AssertionFailedError: X resolution doesn't match in
>>> image file target/test-output/raw_image_demo.pdf-1.bmp expected:<120>
>>> but was:<0>
>>>           at junit.framework.Assert.fail(Assert.java:57)
>>>           at junit.framework.Assert.failNotEquals(Assert.java:329)
>>>           at junit.framework.Assert.assertEquals(Assert.java:78)
>>>           at junit.framework.Assert.assertEquals(Assert.java:234)
>>>           at junit.framework.TestCase.assertEquals(TestCase.java:401)
>>>           at
>>> org.apache.pdfbox.util.TestImageIOUtils.checkBmpResolution(TestImageIOUtils.java:352)
>>>           at
>>> org.apache.pdfbox.util.TestImageIOUtils.checkResolution(TestImageIOUtils.java:300)
>>>           at
>>> org.apache.pdfbox.util.TestImageIOUtils.doTestFile(TestImageIOUtils.java:135)
>>>           at
>>> org.apache.pdfbox.util.TestImageIOUtils.testRenderImage(TestImageIOUtils.java:278)
>>>
>>>
>>> Results :
>>>
>>> Failed tests:
>>>
>>> TestImageIOUtils.testRenderImage:278->doTestFile:135->checkResolution:300->checkBmpResolution:352
>>> X resolution doesn't match in image file
>>> target/test-output/raw_image_demo.pdf-1.bmp expected:<120> but was:<0>
>>>
>>> I'd like to not have to disable all tests in the build.  Could there be
>>> some way to completely disable this functionality?
>> Maybe we should implement an optional switch to disable that part of the test if
>> necessary.
>>
>> @Orion: Is that a possible solution you can live with?
>>
>> BR
>> Andreas Lehmkühler
> I don't see the pom entries on trunk, can this change be made there too?

The trunk build works differently, you would have to add that test to 
the "exclude" list.

Tilman


>
> Thanks,
>
>     Orion
>