Build failed in Jenkins: xmlgraphics-fop-ant #262

2016-12-19 Thread Apache Jenkins Server 
See 

Changes:

[ssteiner] FOP-2674: Update to PDFBox 2.0.4

--
[...truncated 80 lines...]
  2100K .. .. .. .. .. 36% 1.37M 3s
  2150K .. .. .. .. .. 36% 1.68M 3s
  2200K .. .. .. .. .. 37%  130M 2s
  2250K .. .. .. .. .. 38% 83.2M 2s
  2300K .. .. .. .. .. 39%  114M 2s
  2350K .. .. .. .. .. 40%  121M 2s
  2400K .. .. .. .. .. 41% 86.7M 2s
  2450K .. .. .. .. .. 41% 1.38M 2s
  2500K .. .. .. .. .. 42% 1.68M 2s
  2550K .. .. .. .. .. 43% 68.8M 2s
  2600K .. .. .. .. .. 44% 67.4M 2s
  2650K .. .. .. .. .. 45% 77.5M 2s
  2700K .. .. .. .. .. 46% 68.7M 2s
  2750K .. .. .. .. .. 46%  104M 2s
  2800K .. .. .. .. .. 47% 98.4M 2s
  2850K .. .. .. .. .. 48% 1.45M 2s
  2900K .. .. .. .. .. 49% 83.0M 2s
  2950K .. .. .. .. .. 50% 1.69M 2s
  3000K .. .. .. .. .. 51% 82.4M 2s
  3050K .. .. .. .. .. 52% 66.7M 1s
  3100K .. .. .. .. .. 52% 69.5M 1s
  3150K .. .. .. .. .. 53% 70.2M 1s
  3200K .. .. .. .. .. 54% 72.9M 1s
  3250K .. .. .. .. .. 55% 88.5M 1s
  3300K .. .. .. .. .. 56%  113M 1s
  3350K .. .. .. .. .. 57% 1.47M 1s
  3400K .. .. .. .. .. 57% 1.69M 1s
  3450K .. .. .. .. .. 58%  102M 1s
  3500K .. .. .. .. .. 59% 89.4M 1s
  3550K .. .. .. .. .. 60% 95.2M 1s
  3600K .. .. .. .. .. 61% 79.4M 1s
  3650K .. .. .. .. .. 62% 61.1M 1s
  3700K .. .. .. .. .. 62% 66.0M 1s
  3750K .. .. .. .. .. 63% 93.1M 1s
  3800K .. .. .. .. .. 64%  107M 1s
  3850K .. .. .. .. .. 65% 1.50M 1s
  3900K .. .. .. .. .. 66% 77.6M 1s
  3950K .. .. .. .. .. 67% 1.70M 1s
  4000K .. .. .. .. .. 67% 77.3M 1s
  4050K .. .. .. .. .. 68% 97.1M 1s
  4100K .. .. .. .. .. 69% 92.3M 1s
  4150K .. .. .. .. .. 70% 97.7M 1s
  4200K .. .. .. .. .. 71% 83.1M 1s
  4250K .. .. .. .. .. 72% 89.2M 1s
  4300K .. .. .. .. .. 72% 87.1M 1s
  4350K .. .. .. .. .. 73%  113M 1s
  4400K .. .. .. .. .. 74%  113M 1s
  4450K .. .. .. .. .. 75% 1.51M 1s
  4500K .. .. .. .. .. 76% 74.3M 1s
  4550K .. .. .. .. .. 77%  109M 1s
  4600K .. .. .. .. .. 78% 1.70M 1s
  4650K .. .. .. .. .. 78%  101M 0s
  4700K .. .. .. .. .. 79% 71.7M 0s
  4750K .. .. .. .. .. 80% 74.5M 0s
  4800K .. .. .. .. .. 81% 61.5M 0s
  4850K .. .. .. .. .. 82% 73.7M 0s
  4900K .. .. .. .. .. 83% 72.7M 0s
  4950K .. .. .. .. .. 83% 79.0M 0s
  5000K .. .. .. .. .. 84%  115M 0s
  5050K .. .. .. .. .. 85%  130M 0s
  5100K .. .. .. .. .. 86%  130M 0s
  5150K .. .. .. .. .. 87% 28.6M 0s
  5200K .. .. .. .. .. 88% 1.61M 0s
  5250K

[jira] [Comment Edited] (FOP-2523) Behavior change in include path handling breaks existing 1.1 docs

2016-12-19 Thread Graeme Wellington (JIRA) 

[ 
https://issues.apache.org/jira/browse/FOP-2523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15762797#comment-15762797
 ] 

Graeme Wellington edited comment on FOP-2523 at 12/20/16 12:56 AM:
---

My environment is:

Java: jdk1.8.0_111 (64bit)
Tomcat 8.0.15
FOP 1.1
FOP 2.1

I have installed the source for FOP-1.1 and FOP-2.1 and compiled using ANT.

I am testing the XML/XSL PDF generation with a basic XML file and a basic 
Stylesheet with 1 graphic logo.

Command Line


FOP-1.1: 

"C:\fop-2.1\fop.bat" -xml "C:\Temp\42236-050-5002-ELITES-ITEM HIRE.xml" -xsl 
"C:\Temp\BT-PO-SA-ALL.xsl" -pdf "C:\Temp\42236-050-5002-ELITES-ITEM HIRE.pdf" 

Successfully generates PDF

FOP-2.1: 

"C:\fop-2.1\fop.bat" -xml "C:\Temp\42236-050-5002-ELITES-ITEM HIRE.xml" -xsl 
"C:\Temp\BT-PO-SA-ALL.xsl" -pdf "C:\Temp\42236-050-5002-ELITES-ITEM HIRE.pdf" 

Successfully generates PDF

Servlet
===

I loaded the FOP-1.1 fop.war into Tomcat and run the following from IE11:

http://localhost:8500/fop/fop?xml=C:/temp/PO-ELITES-22240-050-5002.xml=C:/temp/BT-PO-SA-ALL.xsl

Successfully rendered PDF to the browser

I then loaded the FOP-2.1 fop.war into Tomcat and run the same command from 
IE11:

http://localhost:8500/fop/fop?xml=C:/temp/PO-ELITES-22240-050-5002.xml=C:/temp/BT-PO-SA-ALL.xsl

This fails with a HTTP error similar to:

HTTP Status 500 - javax.xml.transform.TransformerException: 
org.xml.sax.SAXException: The resource path [file:C:///Temp/logo.jpg] is not 
valid

Followed by a long Exception audit.

If I remove the 1 line where a graphic is referenced with 'fo:external-graphic' 
then the PDF generates ok obviously without the logo.

I have tried various ways to define the source but no luck including:






I have also tried relative paths but no luck.

>From what I have researched it looks like the problem relates to changes in 
>the method used to resolve a URI / URL.

Graeme Wellington
graeme.welling...@ptbuildingsolutions.com.au


was (Author: graeme.wellington):
My environment is:

Java: jdk1.8.0_111 (64bit)
Tomcat 8.0.15
FOP 1.1
FOP 2.1

I have installed the source for FOP-1.1 and FOP-2.1 and compiled using ANT.

I am testing the XML/XSL PDF generation with a basic XML file and a basic 
Stylesheet with 1 

Command Line


FOP-1.1: 

"C:\fop-2.1\fop.bat" -xml "C:\Temp\42236-050-5002-ELITES-ITEM HIRE.xml" -xsl 
"C:\Temp\BT-PO-SA-ALL.xsl" -pdf "C:\Temp\42236-050-5002-ELITES-ITEM HIRE.pdf" 

Successfully generates PDF

FOP-2.1: 

"C:\fop-2.1\fop.bat" -xml "C:\Temp\42236-050-5002-ELITES-ITEM HIRE.xml" -xsl 
"C:\Temp\BT-PO-SA-ALL.xsl" -pdf "C:\Temp\42236-050-5002-ELITES-ITEM HIRE.pdf" 

Successfully generates PDF

Servlet
===

I loaded the FOP-1.1 fop.war into Tomcat and run the following from IE11:

http://localhost:8500/fop/fop?xml=C:/temp/PO-ELITES-22240-050-5002.xml=C:/temp/BT-PO-SA-ALL.xsl

Successfully rendered PDF to the browser

I then loaded the FOP-2.1 fop.war into Tomcat and run the same command from 
IE11:

http://localhost:8500/fop/fop?xml=C:/temp/PO-ELITES-22240-050-5002.xml=C:/temp/BT-PO-SA-ALL.xsl

This fails with a HTTP error similar to:

HTTP Status 500 - javax.xml.transform.TransformerException: 
org.xml.sax.SAXException: The resource path [file:C:///Temp/logo.jpg] is not 
valid

Followed by a long Exception audit.

If I remove the 1 line where a graphic is referenced with 'fo:external-graphic' 
then the PDF generates ok obviously without the logo.

I have tried various ways to define the source but no luck including:






I have also tried relative paths but no luck.

>From what I have researched it looks like the problem relates to changes in 
>the method used to resolve a URI / URL.

Graeme Wellington
graeme.welling...@ptbuildingsolutions.com.au

> Behavior change in include path handling breaks existing 1.1 docs
> -
>
> Key: FOP-2523
> URL: https://issues.apache.org/jira/browse/FOP-2523
> Project: FOP
>  Issue Type: Bug
>  Components: image/jpeg, image/png
>Affects Versions: 2.0
> Environment: OS X , Linux
>Reporter: Johan Persson
>Priority: Minor
>  Labels: path
>
> When transforming a document with included files (images) there is a 
> different behavior between 1.1 and 2.x.
> Transformation that works with fop 1.1 no longer works with 2.0
> I suspect that this is not so much a bug as a change that breaks existing 
> build schemas due to fop making different assumption on relative paths in 1.1 
> compared with 2.x. but I have to yet figure out what the assumption is.
> If the generated .fo includes say, 
> {{}}
> If all files (both images and .fo) are in a flat directory this works well 
> with 1.1. Running the same source through 2.0 will generate an error saying 
> that FOP cannot find the referred file

[jira] [Commented] (FOP-2523) Behavior change in include path handling breaks existing 1.1 docs

2016-12-19 Thread Graeme Wellington (JIRA) 

[ 
https://issues.apache.org/jira/browse/FOP-2523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15762797#comment-15762797
 ] 

Graeme Wellington commented on FOP-2523:


My environment is:

Java: jdk1.8.0_111 (64bit)
Tomcat 8.0.15
FOP 1.1
FOP 2.1

I have installed the source for FOP-1.1 and FOP-2.1 and compiled using ANT.

I am testing the XML/XSL PDF generation with a basic XML file and a basic 
Stylesheet with 1 

Command Line


FOP-1.1: 

"C:\fop-2.1\fop.bat" -xml "C:\Temp\42236-050-5002-ELITES-ITEM HIRE.xml" -xsl 
"C:\Temp\BT-PO-SA-ALL.xsl" -pdf "C:\Temp\42236-050-5002-ELITES-ITEM HIRE.pdf" 

Successfully generates PDF

FOP-2.1: 

"C:\fop-2.1\fop.bat" -xml "C:\Temp\42236-050-5002-ELITES-ITEM HIRE.xml" -xsl 
"C:\Temp\BT-PO-SA-ALL.xsl" -pdf "C:\Temp\42236-050-5002-ELITES-ITEM HIRE.pdf" 

Successfully generates PDF

Servlet
===

I loaded the FOP-1.1 fop.war into Tomcat and run the following from IE11:

http://localhost:8500/fop/fop?xml=C:/temp/PO-ELITES-22240-050-5002.xml=C:/temp/BT-PO-SA-ALL.xsl

Successfully rendered PDF to the browser

I then loaded the FOP-2.1 fop.war into Tomcat and run the same command from 
IE11:

http://localhost:8500/fop/fop?xml=C:/temp/PO-ELITES-22240-050-5002.xml=C:/temp/BT-PO-SA-ALL.xsl

This fails with a HTTP error similar to:

HTTP Status 500 - javax.xml.transform.TransformerException: 
org.xml.sax.SAXException: The resource path [file:C:///Temp/logo.jpg] is not 
valid

Followed by a long Exception audit.

If I remove the 1 line where a graphic is referenced with 'fo:external-graphic' 
then the PDF generates ok obviously without the logo.

I have tried various ways to define the source but no luck including:






I have also tried relative paths but no luck.

>From what I have researched it looks like the problem relates to changes in 
>the method used to resolve a URI / URL.

Graeme Wellington
graeme.welling...@ptbuildingsolutions.com.au

> Behavior change in include path handling breaks existing 1.1 docs
> -
>
> Key: FOP-2523
> URL: https://issues.apache.org/jira/browse/FOP-2523
> Project: FOP
>  Issue Type: Bug
>  Components: image/jpeg, image/png
>Affects Versions: 2.0
> Environment: OS X , Linux
>Reporter: Johan Persson
>Priority: Minor
>  Labels: path
>
> When transforming a document with included files (images) there is a 
> different behavior between 1.1 and 2.x.
> Transformation that works with fop 1.1 no longer works with 2.0
> I suspect that this is not so much a bug as a change that breaks existing 
> build schemas due to fop making different assumption on relative paths in 1.1 
> compared with 2.x. but I have to yet figure out what the assumption is.
> If the generated .fo includes say, 
> {{}}
> If all files (both images and .fo) are in a flat directory this works well 
> with 1.1. Running the same source through 2.0 will generate an error saying 
> that FOP cannot find the referred file (myimage.jpg)
> I suspect this is a common enough pattern to warrant some notice on how to 
> handle this situation.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (FOP-2532) [PATCH] FontCache throws java.lang.IllegalArgumentException: URI scheme is not "file" for jar embedded fonts

2016-12-19 Thread Dave Moten (JIRA) 

[ 
https://issues.apache.org/jira/browse/FOP-2532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15760975#comment-15760975
 ] 

Dave Moten commented on FOP-2532:
-

Can we see this in a release please? When?

> [PATCH] FontCache throws java.lang.IllegalArgumentException: URI scheme is 
> not "file" for jar embedded fonts
> 
>
> Key: FOP-2532
> URL: https://issues.apache.org/jira/browse/FOP-2532
> Project: FOP
>  Issue Type: Bug
>Affects Versions: 2.0
>Reporter: Brian Preuß
>Assignee: simon steiner
> Fix For: trunk
>
> Attachments: lastModified-value-on-opaque-URI.patch
>
>
> If using  fop finds fonts embedded in jar files (via 
> MANIFEST.MF entries as described at 
> http://xmlgraphics.apache.org/fop/2.0/fonts.html#autodetect) and tries to add 
> them to the font cache. This throws the following exception:
> {code}
> java.lang.IllegalArgumentException: URI scheme is not "file"
> 26677/0|  at java.io.File.(File.java:421)
> 26677/0|  at org.apache.fop.fonts.FontCache.addFont(FontCache.java:335)
> 26677/0|  at 
> org.apache.fop.fonts.autodetect.FontInfoFinder.getFontInfoFromCustomFont(FontInfoFinder.java:157)
> 26677/0|  at 
> org.apache.fop.fonts.autodetect.FontInfoFinder.find(FontInfoFinder.java:269)
> 26677/0|  at org.apache.fop.fonts.FontAdder.add(FontAdder.java:63)
> 26677/0|  at 
> org.apache.fop.fonts.FontDetectorFactory$DefaultFontDetector.detect(FontDetectorFactory.java:110)
> 26677/0|  at 
> org.apache.fop.fonts.FontManager.autoDetectFonts(FontManager.java:229)
> 26677/0|  at 
> org.apache.fop.fonts.DefaultFontConfigurator.configure(DefaultFontConfigurator.java:82)
> 26677/0|  at 
> org.apache.fop.render.PrintRendererConfigurator.getCustomFontCollection(PrintRendererConfigurator.java:147)
> 26677/0|  at 
> org.apache.fop.render.PrintRendererConfigurator.setupFontInfo(PrintRendererConfigurator.java:127)
> 26677/0|  at 
> org.apache.fop.render.intermediate.IFUtil.setupFonts(IFUtil.java:170)
> 26677/0|  at 
> org.apache.fop.render.intermediate.IFRenderer.setupFontInfo(IFRenderer.java:187)
> 26677/0|  at 
> org.apache.fop.area.RenderPagesModel.(RenderPagesModel.java:75)
> 26677/0|  at 
> org.apache.fop.area.AreaTreeHandler.setupModel(AreaTreeHandler.java:135)
> 26677/0|  at 
> org.apache.fop.area.AreaTreeHandler.(AreaTreeHandler.java:105)
> 26677/0|  at 
> org.apache.fop.render.RendererFactory.createFOEventHandler(RendererFactory.java:350)
> 26677/0|  at 
> org.apache.fop.fo.FOTreeBuilder.(FOTreeBuilder.java:107)
> 26677/0|  at org.apache.fop.apps.Fop.createDefaultHandler(Fop.java:104)
> 26677/0|  at org.apache.fop.apps.Fop.(Fop.java:78)
> 26677/0|  at org.apache.fop.apps.FOUserAgent.newFop(FOUserAgent.java:179)
> 26677/0|  at org.apache.fop.apps.FopFactory.newFop(FopFactory.java:240)
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (FOP-2674) Update to PDFBox 2.0.4

2016-12-19 Thread simon steiner (JIRA) 

[ 
https://issues.apache.org/jira/browse/FOP-2674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15760877#comment-15760877
 ] 

simon steiner commented on FOP-2674:


http://svn.apache.org/viewvc?view=revision=1775054
http://svn.apache.org/viewvc?view=revision=1775056

> Update to PDFBox 2.0.4
> --
>
> Key: FOP-2674
> URL: https://issues.apache.org/jira/browse/FOP-2674
> Project: FOP
>  Issue Type: Bug
>Reporter: simon steiner
>Assignee: simon steiner
>
> Many bug fixes



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (FOP-2674) Update to PDFBox 2.0.4

2016-12-19 Thread simon steiner (JIRA) 

 [ 
https://issues.apache.org/jira/browse/FOP-2674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

simon steiner resolved FOP-2674.

Resolution: Fixed

> Update to PDFBox 2.0.4
> --
>
> Key: FOP-2674
> URL: https://issues.apache.org/jira/browse/FOP-2674
> Project: FOP
>  Issue Type: Bug
>Reporter: simon steiner
>Assignee: simon steiner
>
> Many bug fixes



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (FOP-2674) Update to PDFBox 2.0.4

2016-12-19 Thread simon steiner (JIRA) 

 [ 
https://issues.apache.org/jira/browse/FOP-2674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

simon steiner updated FOP-2674:
---
Description: Many bug fixes  (was: Many bug fixes and CVE-2016-2175)

> Update to PDFBox 2.0.4
> --
>
> Key: FOP-2674
> URL: https://issues.apache.org/jira/browse/FOP-2674
> Project: FOP
>  Issue Type: Bug
>Reporter: simon steiner
>Assignee: simon steiner
>
> Many bug fixes



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (FOP-2674) Update to PDFBox 2.0.4

2016-12-19 Thread simon steiner (JIRA) 
simon steiner created FOP-2674:
--

 Summary: Update to PDFBox 2.0.4
 Key: FOP-2674
 URL: https://issues.apache.org/jira/browse/FOP-2674
 Project: FOP
  Issue Type: Bug
Reporter: simon steiner
Assignee: simon steiner


Many bug fixes and CVE-2016-2175



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)