You are viewing a plain text version of this content. The canonical link for it is here.
Posted to fop-dev@xmlgraphics.apache.org by Jan Tosovsky <j....@email.cz> on 2016/07/26 20:15:45 UTC

Building from current TRUNK fails

Dear All,

I've updated local copy to the current (mavenized) version and I am unable
build (Oracle JDK 1.8) the FOP Core project:
(1) testAES256() fails with 
java.lang.IllegalStateException: java.security.InvalidKeyException: Illegal
key size
	at javax.crypto.Cipher.checkCryptoPerm(Cipher.java:1034)
      ...
	at
o.a.f.pdf.PDFEncryptionJCETestCase.testAES256(PDFEncryptionJCETestCase.java:
468)

(2) there is missing reference to JAI in
o.a.f.util.bitmap.JAIMonochromeBitmapConverter.java

Both indicate there is additional configuring steps required, but the
'build' page hasn't been updated yet:
http://xmlgraphics.apache.org/fop/trunk/compiling.html (there is still Ant
mentioned)

Is there any reason JAI is not part of pom file?

Thanks,

Jan


Re: Building from current TRUNK fails

Posted by Jacopo Cappellato <ja...@gmail.com>.
On Tue, Jul 26, 2016 at 10:35 PM, Andreas Delmelle <
andreas.delmelle@telenet.be> wrote:

> Hi Jan
>
> > On 26 Jul 2016, at 22:15, Jan Tosovsky <j....@email.cz> wrote:
> >
> > Dear All,
> >
> > I've updated local copy to the current (mavenized) version and I am
> unable
> > build (Oracle JDK 1.8) the FOP Core project:
> > (1) testAES256() fails with
> > java.lang.IllegalStateException: java.security.InvalidKeyException:
> Illegal
> > key size
> >       at javax.crypto.Cipher.checkCryptoPerm(Cipher.java:1034)
> >      ...
> >       at
> > o.a.f.pdf.PDFEncryptionJCETestCase.testAES256(
> PDFEncryptionJCETestCase.java:
> > 468)
>
> Are you on OS X/macOS?
> I am not entirely sure, but I seem to recall running into that as well. It
> just means you need to download the "unlimited strength" encryption policy
> files from Oracle. They made that a separate download, just like in the
> good old Sun days. On OS X, when Apple maintained their own JDK, it was
> always included. I only ran into that after Apple abandoned maintenance of
> the JDK for OS X...
>
> see - http://www.oracle.com/technetwork/java/javase/
> downloads/jce8-download-2133166.html


I am on OS X and I can confirm I had the same issue and the solution
proposed by Adreas did the trick, thank you!

Jacopo

RE: Building from current TRUNK fails

Posted by Jan Tosovsky <j....@email.cz>.
On 2016-07-26 Jan Tosovsky wrote:
> On 2016-07-26 Andreas Delmelle wrote:
> > > On 2016-07-26 Jan Tosovsky wrote:
> > >
> > > (2) there is missing reference to JAI in
> > > o.a.f.util.bitmap.JAIMonochromeBitmapConverter.java
> > >
> > > Is there any reason JAI is not part of pom file?
> >
> > I know that one as well. What I usually do to make FOP compile 
> > after a fresh trunk checkout, is just delete that source file 
> > locally (i.e. just a regular "rm", not an "svn del").
> >
> 
> This is not actually a build blocker.

Ha, I've found this config in the POM file which explains why build doesn't
fail...

      <!-- compile exclusions -->
      <plugin>
        <artifactId>maven-compiler-plugin</artifactId>
        <configuration>
          <excludes>
 
<exclude>org/apache/fop/util/bitmap/JAIMonochromeBitmapConverter.java</exclu
de>
          </excludes>
        </configuration>
      </plugin>

Jan




RE: Building from current TRUNK fails

Posted by Jan Tosovsky <j....@email.cz>.
On 2016-07-26 Andreas Delmelle wrote:
> > On 2016-07-26 Jan Tosovsky wrote:
> >
> > I've updated local copy to the current (mavenized) version and I am
> > unable build (Oracle JDK 1.8) the FOP Core project:
> > (1) testAES256() fails with
> > java.lang.IllegalStateException: java.security.InvalidKeyException:
> 
> It just means you need to download the "unlimited strength" encryption
> policy files from Oracle. They made that a separate download, ...
> see http://www.oracle.com/technetwork/java/javase/downloads/jce8-
> download-2133166.html

thanks, that helped!

> > (2) there is missing reference to JAI in
> > o.a.f.util.bitmap.JAIMonochromeBitmapConverter.java
> >
> > Is there any reason JAI is not part of pom file?
> 
> I know that one as well. What I usually do to make FOP compile after a
> fresh trunk checkout, is just delete that source file locally (i.e.
> just a regular "rm", not an "svn del").
> 

This is not actually a build blocker. As JAI seems to be abandoned (for
image manipulations I prefer https://github.com/haraldk/TwelveMonkeys/
library), I suggest deleting this file completely ;-) 

Jan


Re: Building from current TRUNK fails

Posted by Andreas Delmelle <an...@telenet.be>.
Hi Jan

> On 26 Jul 2016, at 22:15, Jan Tosovsky <j....@email.cz> wrote:
> 
> Dear All,
> 
> I've updated local copy to the current (mavenized) version and I am unable
> build (Oracle JDK 1.8) the FOP Core project:
> (1) testAES256() fails with 
> java.lang.IllegalStateException: java.security.InvalidKeyException: Illegal
> key size
> 	at javax.crypto.Cipher.checkCryptoPerm(Cipher.java:1034)
>      ...
> 	at
> o.a.f.pdf.PDFEncryptionJCETestCase.testAES256(PDFEncryptionJCETestCase.java:
> 468)

Are you on OS X/macOS? 
I am not entirely sure, but I seem to recall running into that as well. It just means you need to download the "unlimited strength" encryption policy files from Oracle. They made that a separate download, just like in the good old Sun days. On OS X, when Apple maintained their own JDK, it was always included. I only ran into that after Apple abandoned maintenance of the JDK for OS X...

see - http://www.oracle.com/technetwork/java/javase/downloads/jce8-download-2133166.html

> 
> (2) there is missing reference to JAI in
> o.a.f.util.bitmap.JAIMonochromeBitmapConverter.java
> 
> Both indicate there is additional configuring steps required, but the
> 'build' page hasn't been updated yet:
> http://xmlgraphics.apache.org/fop/trunk/compiling.html (there is still Ant
> mentioned)
> 
> Is there any reason JAI is not part of pom file?

I know that one as well. What I usually do to make FOP compile after a fresh trunk checkout, is just delete that source file locally (i.e. just a regular "rm", not an "svn del").


Hope this helps!

Cheers

Andreas