Thanks Glenn. I'm not worried about this as I just changed the maven
runner to use 1.7 and left the project language level as 1.6, which also
worked.
+1 for the merge
Chris
On 17/03/2016 12:08, Glenn Adams wrote:
This problem is apparently caused by a higher security level for SSL on
repository.apache.com that is normally handled by JDK 1.6 (unlimited
security), which turns out to not really by unlimited. See [1] as pointed
out by Simon.
[1] https://issues.apache.org/jira/browse/INFRA-10298
I fixed this on my local machine by installing bouncy castle as described
in [2], except I used:
Here are the steps I took using Java 1.6.0_65-b14-462 on Mac OSC 10.7.5
1) Download these jars:
bcprov-jdk15on-152.jar
<https://www.bouncycastle.org/download/bcprov-jdk15on-152.jar>
bcprov-ext-jdk15on-152.jar
<https://www.bouncycastle.org/download/bcprov-ext-jdk15on-152.jar>2) move
these jars to $JAVA_HOME/lib/ext
3) edit $JAVA_HOME/lib/security/java.security as follows:
security.provider.1=org.bouncycastle.jce.provider.BouncyCastleProvider
For this last line, you may have to tweak the order. I used
security.provider.3.
[2]
http://stackoverflow.com/questions/6851461/java-why-does-ssl-handshake-give-could-not-generate-dh-keypair-exception
On Thu, Mar 17, 2016 at 5:15 AM, Chris Bowditch <[email protected]>
wrote:
Sorry been a bit busy, but I get the following error on fresh checkout and
running install:
Could not transfer artifact
org.apache.xmlgraphics:fop-util:pom:2.2.0-SNAPSHOT from/to
apache.snapshots.https (
https://repository.apache.org/content/repositories/snapshots):
java.lang.RuntimeException: Could not generate DH keypair: Prime size must
be multiple of 64, and can only range from 512 to 1024 (inclusive) -> [Help
1]
Simon mentioned I need to change to Java 7 to resolve, but we have not yet
agreed to upgrade the minimum version.
On 16/03/2016 17:03, Glenn Adams wrote:
Voting was a bit thin, but there were no objections. Therefore, I will
proceed with the merge.
On Sat, Mar 12, 2016 at 8:13 PM, Glenn Adams <[email protected]> wrote:
I would like to start a vote on merging from
xmlgraphics/fop/branches/maven
[1] to trunk [2]. Please respond by Wednesday, 03/16, 1700Z. Lack of a
response will be interpreted as +0.
[1] http://svn.apache.org/repos/asf/xmlgraphics/fop/branches/maven/
[2] http://svn.apache.org/repos/asf/xmlgraphics/fop/trunk/
The following run without error (on my platform) using both JDK 1.6 and
1.7:
- ant -f fop/build.xml clean all checkstyle findbugs
- mvn clean install checkstyle:check findbugs:check -U
I am using the following tool versions (with JDK 1.6 enabled):
bash-3.2$ mvn -v
Apache Maven 3.2.5 (12a6b3acb947671f09b81f49094c53f426d8cea1;
2014-12-14T10:29:23-07:00)
Maven home: /opt/local/share/java/maven32
Java version: 1.6.0_65, vendor: Apple Inc.
Java home: /Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home
Default locale: en_US, platform encoding: MacRoman
OS name: "mac os x", version: "10.11.3", arch: "x86_64", family: "mac"
bash-3.2$ ant -version
Apache Ant(TM) version 1.9.6 compiled on June 29 2015
A Jenkins build project is running (without error) at [3], wherein both
checkstyle and findbugs analyses are enabled by default.
[3] https://builds.apache.org/job/xmlgraphics-fop-maven/
Notes:
1. the ant build is run from the fop subdirectory of [1];
2. all build artifacts (fop, fop-sandbox, fop-servlet,
fop-transcoder,
fop-transcoder-allinone) have been verified for content;
3. source code is now distributed between fop-util, fop-events, and
fop-core modules; this was needed to eliminate a circular dependency
between fop and the generation of event infrastructure; i expect some
further fine-tuning to occur here over time;
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
