You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@pdfbox.apache.org by Andreas Lehmkuehler <an...@lehmi.de> on 2014/05/02 18:26:57 UTC
[ANNOUNCE] Apache PDFBox 1.8.5 released
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
See the full release notes below for details about this release.
Release Notes -- Apache PDFBox -- Version 1.8.5
Introduction
------------
The Apache PDFBox library is an open source Java tool for working with PDF
documents.
This is an incremental bugfix release based on the earlier 1.8.4 release. It
contains a couple of fixes and small improvements.
For more details on all fixes included in this release, please refer to the
following
issues on the PDFBox issue tracker at https://issues.apache.org/jira/browse/PDFBOX.
Bug
[PDFBOX-198] - Tiff image problems
[PDFBOX-205] - Miscellaneous errors on valid files
[PDFBOX-778] - OutOfMemory when extracting text from pdf
[PDFBOX-1069] - Ubuntu throws exceptions when fonts missing
[PDFBOX-1074] - TIFFFaxDecoder5 when using PDFImageWriter
[PDFBOX-1147] - Printing a PDF with an image inside show black.
[PDFBOX-1164] - Inline image parsing error causes RuntimeException + FIX
[PDFBOX-1664] - NullPointerException in PDType1Font.java
[PDFBOX-1708] - IndexOutOfBoundsException on convertToImage with an embedded
Fax-Image
[PDFBOX-1811] - java.io.IOException: Object at offset does not end with 'endobj'
[PDFBOX-1860] - HTML converter escapes formatting close tags
[PDFBOX-1870] - PDFunctionType0 incorrect
[PDFBOX-1876] - Incorrect color for DeviceN type 4 shading object
[PDFBOX-1877] - Radial Shading (type 3) fails Ghent Workgroup tests
[PDFBOX-1880] - [PATCH] Type 1 Shading must not ignore current transformation matrix
[PDFBOX-1882] - Negative array size exception when reading a string from a OTF font
[PDFBOX-1884] - Avoid NPE when encountering null PDComplexFileSpecification
[PDFBOX-1887] - Bugfixes + Optimization of Gouraud Shading
[PDFBOX-1888] - JBIG2Filter is creating an ImageInputStream (with temp file) and not
closing it
[PDFBOX-1896] - Support MMType1 (Multiple Master) Fonts
[PDFBOX-1901] - null check confusing
[PDFBOX-1917] - Rendering hangs
[PDFBOX-1924] - Gouraud shading: detect empty triangles
[PDFBOX-1966] - Type 1, 4 and 5 shadings for shFill()
[PDFBOX-1970] - 1.8 shadings are sometimes flipped
[PDFBOX-1977] - LZWFilter fails
[PDFBOX-1984] - PDFont documentation correction needed for getFontWidth and
getFontHeight
[PDFBOX-1988] - PDFBox ExtractText issue of PDF with no embedded fonts
[PDFBOX-1998] - PDF rendering with reversed colors
[PDFBOX-1999] - JBIG2Filter - FlateDecoded Globals Table
[PDFBOX-2004] - PDF2Image hangs/loops forever processing PDF
[PDFBOX-2008] - Off-by-one error in BaseParser.readGenerationNumber()
[PDFBOX-2016] - Stream parsing still incorrect if length value is wrong
[PDFBOX-2018] - Dashed line with incorrect line cap
[PDFBOX-2024] - /Rotate 180 PDF is not displayed correctly in PDFReader app
[PDFBOX-2026] - cannot load jpg into new pdf
[PDFBOX-2030] - Using new PDPixelMap() results in black image in PDF
[PDFBOX-2031] - GrayScale images become inverted
[PDFBOX-2032] - [PATCH] TTF Type12 IOException: Invalid Characters codes
[PDFBOX-2035] - Ignore badly formatted toUnicode CMaps
[PDFBOX-2036] - Add test with LZW fail sequence
[PDFBOX-2042] - ColorSpace with empty Range array
Improvement
[PDFBOX-52] - DCTFilter is not implemented yet
[PDFBOX-615] - shfill operator needs implementation
[PDFBOX-1734] - ImageIoUtil.WriteImage doesn't work with tiff images
[PDFBOX-1869] - Implementation for ShadingType 1
[PDFBOX-1897] - There are some errors within the source code documentation
(javadocs)
[PDFBOX-1902] - generics added to maputil
[PDFBOX-1909] - Close open streams
[PDFBOX-1914] - Shading package: Move "function" methods to base class and more
refactoring
[PDFBOX-1946] - Running within an Applet has many AccessControlException 's
[PDFBOX-1964] - PDFMergerUtility support merging using non sequential parser
[PDFBOX-1975] - Improve TestImageIOUtils unit tests to check image resolution and
compression
[PDFBOX-2010] - make "protected PDFont getDescendantFont()" public as it is in 2.0.0
[PDFBOX-2039] - Class PDDocument should implement java.io.Closeable
Release Contents
----------------
This release consists of a single source archive packaged as a zip file.
The archive can be unpacked with the jar tool from your JDK installation.
See the README.txt file for instructions on how to build this release.
The source archive is accompanied by SHA1 and MD5 checksums and a PGP
signature that you can use to verify the authenticity of your download.
The public key used for the PGP signature can be found at
https://svn.apache.org/repos/asf/pdfbox/KEYS.
About Apache PDFBox
-------------------
Apache PDFBox is an open source Java library for working with PDF documents.
This project allows creation of new PDF documents, manipulation of existing
documents and the ability to extract content from documents. Apache PDFBox
also includes several command line utilities. Apache PDFBox is published
under the Apache License, Version 2.0.
For more information, visit http://pdfbox.apache.org/
About The Apache Software Foundation
------------------------------------
Established in 1999, The Apache Software Foundation provides organizational,
legal, and financial support for more than 100 freely-available,
collaboratively-developed Open Source projects. The pragmatic Apache License
enables individual and commercial users to easily deploy Apache software;
the Foundation's intellectual property framework limits the legal exposure
of its 2,500+ contributors.
For more information, visit http://www.apache.org/
Re: [ANNOUNCE] Apache PDFBox 1.8.5 released
Posted by Tilman Hausherr <TH...@t-online.de>.
If you don't have these two files more tests in TestImageIOUtils will
fail. The easiest way is probably to delete the line with
TestImageIOUtils in the file TestAll.java.
Tilman
Am 15.05.2014 06:20, schrieb Orion Poplawski:
> On 05/13/2014 11:59 PM, Tilman Hausherr wrote:
>> Am 08.05.2014 05:17, schrieb Orion Poplawski:
>>> 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.
>> Sorry for the late answer, apache lost a few disks.
>> https://blogs.apache.org/infra/entry/mail_outage
>>
>> Why do you need to "disable access" ? These two jars are need for the
>> tests. They are loaded remotely in the build because we can't distribute
>> them.
> Fedora builders cannot access anything remotely (security and
> reproducibility concerns).
>
>>> 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>
>> This test is done in TestImageIOUtils.java, it writes a .BMP file and
>> rereads it and checks if the resolution is there. It needs
>> jai_imageio.jar to succeed because the default imageio doesn't work
>> properly.
>>
>> There are these 4 lines:
>>
>> // testing BMP
>> imageType = "bmp";
>> writeImage(document, imageType, outDir + file.getName() +
>> "-", ImageType.RGB, dpi);
>> checkResolution(outDir + file.getName() + "-1." + imageType,
>> (int) dpi);
>>
>> remove the last one.
>>
>> However if you disable access to the two jars, more tests in
>> TestImageIOUtils will fail.
>>
>> Tilman (who did these changes)
>>
>>
>>> I'd like to not have to disable all tests in the build. Could there be
>>> some way to completely disable this functionality?
>>>
>>> Thanks.
>>>
>>> - Orion
>>>
>
Re: [ANNOUNCE] Apache PDFBox 1.8.5 released
Posted by Orion Poplawski <or...@cora.nwra.com>.
On 05/13/2014 11:59 PM, Tilman Hausherr wrote:
> Am 08.05.2014 05:17, schrieb Orion Poplawski:
>> 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.
>
> Sorry for the late answer, apache lost a few disks.
> https://blogs.apache.org/infra/entry/mail_outage
>
> Why do you need to "disable access" ? These two jars are need for the
> tests. They are loaded remotely in the build because we can't distribute
> them.
Fedora builders cannot access anything remotely (security and
reproducibility concerns).
>
>> 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>
>
> This test is done in TestImageIOUtils.java, it writes a .BMP file and
> rereads it and checks if the resolution is there. It needs
> jai_imageio.jar to succeed because the default imageio doesn't work
> properly.
>
> There are these 4 lines:
>
> // testing BMP
> imageType = "bmp";
> writeImage(document, imageType, outDir + file.getName() +
> "-", ImageType.RGB, dpi);
> checkResolution(outDir + file.getName() + "-1." + imageType,
> (int) dpi);
>
> remove the last one.
>
> However if you disable access to the two jars, more tests in
> TestImageIOUtils will fail.
>
> Tilman (who did these changes)
>
>
>>
>> I'd like to not have to disable all tests in the build. Could there be
>> some way to completely disable this functionality?
>>
>> Thanks.
>>
>> - Orion
>>
--
Orion Poplawski
Technical Manager 303-415-9701 x222
NWRA/CoRA Division FAX: 303-415-9702
3380 Mitchell Lane orion@cora.nwra.com
Boulder, CO 80301 http://www.cora.nwra.com
Re: [ANNOUNCE] Apache PDFBox 1.8.5 released
Posted by Tilman Hausherr <TH...@t-online.de>.
Am 08.05.2014 05:17, schrieb Orion Poplawski:
> 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.
Sorry for the late answer, apache lost a few disks.
https://blogs.apache.org/infra/entry/mail_outage
Why do you need to "disable access" ? These two jars are need for the
tests. They are loaded remotely in the build because we can't distribute
them.
> 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>
This test is done in TestImageIOUtils.java, it writes a .BMP file and
rereads it and checks if the resolution is there. It needs
jai_imageio.jar to succeed because the default imageio doesn't work
properly.
There are these 4 lines:
// testing BMP
imageType = "bmp";
writeImage(document, imageType, outDir + file.getName() +
"-", ImageType.RGB, dpi);
checkResolution(outDir + file.getName() + "-1." +
imageType, (int) dpi);
remove the last one.
However if you disable access to the two jars, more tests in
TestImageIOUtils will fail.
Tilman (who did these changes)
>
> I'd like to not have to disable all tests in the build. Could there be
> some way to completely disable this functionality?
>
> Thanks.
>
> - Orion
>
Re: Disabling TestImageIOUtils
Posted by Tilman Hausherr <TH...@t-online.de>.
Am 18.06.2014 06:34, schrieb Orion Poplawski:
> On 05/16/2014 03:53 AM, Andreas Lehmkühler wrote:
>> Hi,
>>
>>
>>> Orion Poplawski <or...@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
>
Re:Disabling TestImageIOUtils
Posted by Orion Poplawski <or...@cora.nwra.com>.
On 05/16/2014 03:53 AM, Andreas Lehmkühler wrote:
> Hi,
>
>
>> Orion Poplawski <or...@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?
Thanks,
Orion
--
Orion Poplawski
Technical Manager 303-415-9701 x222
NWRA/CoRA Division FAX: 303-415-9702
3380 Mitchell Lane orion@cora.nwra.com
Boulder, CO 80301 http://www.cora.nwra.com
Re: [ANNOUNCE] Apache PDFBox 1.8.5 released
Posted by Orion Poplawski <or...@cora.nwra.com>.
On 05/19/2014 02:07 PM, Tilman Hausherr wrote:
> @Andreas: Yes, but he'll have to remove the segment with the dependencies too.
>
> @Orion: does the currrent solution satisfy you? If not, any suggestions? If
> yes, what will the fedora folks do now - just change the two files, or skip
> this release and wait for the next one?
>
> Tilman
That's working well for me, thanks a lot. I back-ported the change to 1.8.5.
Now though we are stuck on bouncycastle 1.50:
https://issues.apache.org/jira/browse/PDFBOX-2088
It never ends...
- Orion
--
Orion Poplawski
Technical Manager 303-415-9701 x222
NWRA, Boulder/CoRA Office FAX: 303-415-9702
3380 Mitchell Lane orion@nwra.com
Boulder, CO 80301 http://www.nwra.com
Re: [ANNOUNCE] Apache PDFBox 1.8.5 released
Posted by Tilman Hausherr <TH...@t-online.de>.
@Andreas: Yes, but he'll have to remove the segment with the
dependencies too.
@Orion: does the currrent solution satisfy you? If not, any suggestions?
If yes, what will the fedora folks do now - just change the two files,
or skip this release and wait for the next one?
Tilman
Am 19.05.2014 21:15, schrieb Andreas Lehmkuehler:
> Hi,
>
> Am 19.05.2014 20:11, schrieb Tilman Hausherr:
>> Yes I opened
>> https://issues.apache.org/jira/browse/PDFBOX-2084
>> and already did the first part.
> Cool, and thanks!!
>
>> Then I saw that you wrote about "an optional switch", I'll have to do
>> some
>> reading about maven syntax first. Probably the solution is to have
>> several maven
>> profiles.
> That was a misunderstanding. I thought about about a switch in the
> test case to
> enable/disable that part of the test. IMHO it's already handy enough
> to simply
> remove one line from the pom to disable the test.
>
>>
>> Tilman
>>
>
> BR
> Andreas Lehmkühler
>
>> Am 19.05.2014 11:47, schrieb Andreas Lehmkühler:
>>> Hi,
>>>
>>>> Tilman Hausherr <TH...@t-online.de> hat am 18. Mai 2014 um 14:10
>>>> geschrieben:
>>>>
>>>>
>>>> The easiest way would be
>>>> - remove TestImageIOUtils from TestAll
>>>> - add it as a single test to the pom
>>>>
>>>> In that case, you (Orion) would only have to touch the pom, i.e.
>>>> delete
>>>> the line with TestImageIOUtils and the segment with the two
>>>> dependencies.
>>>>
>>>> Is that what you had in mind?
>>>>
>>>> I just tested it, it builds.
>>> +1, looks good to me and I guess that's what Orion is looking for.
>>>
>>> @Tilman
>>> Can you take care about this?
>>>
>>>> Tilman
>>>>
>>>> Am 18.05.2014 04:27, schrieb Orion Poplawski:
>>>>>>>>> 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
>>>>> That would be wonderful. We can do all kinds of pom.xml
>>>>> manipulation as
>>>>> well pretty easily if needed. But some kind of switch to disable
>>>>> using
>>>>> these jars would be great.
>>> BR
>>> Andreas Lehmkühler
>>
>
Re: [ANNOUNCE] Apache PDFBox 1.8.5 released
Posted by Andreas Lehmkuehler <an...@lehmi.de>.
Hi,
Am 19.05.2014 20:11, schrieb Tilman Hausherr:
> Yes I opened
> https://issues.apache.org/jira/browse/PDFBOX-2084
> and already did the first part.
Cool, and thanks!!
> Then I saw that you wrote about "an optional switch", I'll have to do some
> reading about maven syntax first. Probably the solution is to have several maven
> profiles.
That was a misunderstanding. I thought about about a switch in the test case to
enable/disable that part of the test. IMHO it's already handy enough to simply
remove one line from the pom to disable the test.
>
> Tilman
>
BR
Andreas Lehmkühler
> Am 19.05.2014 11:47, schrieb Andreas Lehmkühler:
>> Hi,
>>
>>> Tilman Hausherr <TH...@t-online.de> hat am 18. Mai 2014 um 14:10
>>> geschrieben:
>>>
>>>
>>> The easiest way would be
>>> - remove TestImageIOUtils from TestAll
>>> - add it as a single test to the pom
>>>
>>> In that case, you (Orion) would only have to touch the pom, i.e. delete
>>> the line with TestImageIOUtils and the segment with the two dependencies.
>>>
>>> Is that what you had in mind?
>>>
>>> I just tested it, it builds.
>> +1, looks good to me and I guess that's what Orion is looking for.
>>
>> @Tilman
>> Can you take care about this?
>>
>>> Tilman
>>>
>>> Am 18.05.2014 04:27, schrieb Orion Poplawski:
>>>>>>>> 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
>>>> That would be wonderful. We can do all kinds of pom.xml manipulation as
>>>> well pretty easily if needed. But some kind of switch to disable using
>>>> these jars would be great.
>> BR
>> Andreas Lehmkühler
>
Re: [ANNOUNCE] Apache PDFBox 1.8.5 released
Posted by Tilman Hausherr <TH...@t-online.de>.
Yes I opened
https://issues.apache.org/jira/browse/PDFBOX-2084
and already did the first part.
Then I saw that you wrote about "an optional switch", I'll have to do
some reading about maven syntax first. Probably the solution is to have
several maven profiles.
Tilman
Am 19.05.2014 11:47, schrieb Andreas Lehmkühler:
> Hi,
>
>> Tilman Hausherr <TH...@t-online.de> hat am 18. Mai 2014 um 14:10
>> geschrieben:
>>
>>
>> The easiest way would be
>> - remove TestImageIOUtils from TestAll
>> - add it as a single test to the pom
>>
>> In that case, you (Orion) would only have to touch the pom, i.e. delete
>> the line with TestImageIOUtils and the segment with the two dependencies.
>>
>> Is that what you had in mind?
>>
>> I just tested it, it builds.
> +1, looks good to me and I guess that's what Orion is looking for.
>
> @Tilman
> Can you take care about this?
>
>> Tilman
>>
>> Am 18.05.2014 04:27, schrieb Orion Poplawski:
>>>>>>> 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
>>> That would be wonderful. We can do all kinds of pom.xml manipulation as
>>> well pretty easily if needed. But some kind of switch to disable using
>>> these jars would be great.
> BR
> Andreas Lehmkühler
Re: [ANNOUNCE] Apache PDFBox 1.8.5 released
Posted by Andreas Lehmkühler <an...@lehmi.de>.
Hi,
> Tilman Hausherr <TH...@t-online.de> hat am 18. Mai 2014 um 14:10
> geschrieben:
>
>
> The easiest way would be
> - remove TestImageIOUtils from TestAll
> - add it as a single test to the pom
>
> In that case, you (Orion) would only have to touch the pom, i.e. delete
> the line with TestImageIOUtils and the segment with the two dependencies.
>
> Is that what you had in mind?
>
> I just tested it, it builds.
+1, looks good to me and I guess that's what Orion is looking for.
@Tilman
Can you take care about this?
> Tilman
>
> Am 18.05.2014 04:27, schrieb Orion Poplawski:
> >>> >>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
> > That would be wonderful. We can do all kinds of pom.xml manipulation as
> > well pretty easily if needed. But some kind of switch to disable using
> > these jars would be great.
>
BR
Andreas Lehmkühler
Re: [ANNOUNCE] Apache PDFBox 1.8.5 released
Posted by Tilman Hausherr <TH...@t-online.de>.
The easiest way would be
- remove TestImageIOUtils from TestAll
- add it as a single test to the pom
In that case, you (Orion) would only have to touch the pom, i.e. delete
the line with TestImageIOUtils and the segment with the two dependencies.
Is that what you had in mind?
I just tested it, it builds.
Tilman
Am 18.05.2014 04:27, schrieb Orion Poplawski:
>>> >>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
> That would be wonderful. We can do all kinds of pom.xml manipulation as
> well pretty easily if needed. But some kind of switch to disable using
> these jars would be great.
Re: [ANNOUNCE] Apache PDFBox 1.8.5 released
Posted by Orion Poplawski <or...@cora.nwra.com>.
On 05/16/2014 03:53 AM, Andreas Lehmkühler wrote:
> Hi,
>
>
>> Orion Poplawski <or...@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
That would be wonderful. We can do all kinds of pom.xml manipulation as
well pretty easily if needed. But some kind of switch to disable using
these jars would be great.
--
Orion Poplawski
Technical Manager 303-415-9701 x222
NWRA/CoRA Division FAX: 303-415-9702
3380 Mitchell Lane orion@cora.nwra.com
Boulder, CO 80301 http://www.cora.nwra.com
Re: [ANNOUNCE] Apache PDFBox 1.8.5 released
Posted by Andreas Lehmkühler <an...@lehmi.de>.
Hi,
> Orion Poplawski <or...@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
Re: [ANNOUNCE] Apache PDFBox 1.8.5 released
Posted by Orion Poplawski <or...@cora.nwra.com>.
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?
Thanks.
- Orion
--
Orion Poplawski
Technical Manager 303-415-9701 x222
NWRA/CoRA Division FAX: 303-415-9702
3380 Mitchell Lane orion@cora.nwra.com
Boulder, CO 80301 http://www.cora.nwra.com