Re: [forge-dev] Building Forge with Java 8
----- Original Message -----
From: "Ivan St. Ivanov" <ivan.st.ivanov(a)gmail.com>
To: "forge-dev List" <forge-dev(a)lists.jboss.org>
Cc: "Mani Sarkar" <sadhak001(a)gmail.com>
Sent: Wednesday, November 26, 2014 2:38:45 PM
Subject: [forge-dev] Building Forge with Java 8
Hi everybody,
As some of you noticed, last night I was able to build and run Forge with the
latest early access build of Open JDK 9 (from the Jigsaw forest!). I had to
do just one manual workaround. I had to manually add the following
dependency to the javaee/impl/pom.xml and shell/impl/pom.xml:
<dependency>
<groupId>org.jboss.forge.furnace.container</groupId>
<artifactId>simple-api</artifactId>
<scope>provided</scope>
</dependency>
It was a problem that was already found and documented in this JIRA:
https://issues.jboss.org/browse/FORGE-2019
The JIRA says that this problem occurs with Java 8, build 20. So my question
is whether this is fixed in later builds of Java 8. If yes, I will report
this to the Open JDK folks to up-port the fix to Java 9 as well. If not, I
guess we should fix the poms of the respective projects?
I believe this is a known bug in OpenJDK (link anyone?) and it has broken other project
builds as well.
It is unfixed as of 8u25 (tested it yesterday), so we're using older versions of JDK
to build Forge.
And the POMs should not be fixed; that would be the wrong way to go about it (see
George's comment in the JIRA).
Thanks,
Ivan
P.S. Sorry for the 'lazy web' style of message. I know I could have run the
build with newer Java 8 by myself :)
P.P.S. Thanks to Mani Sarkar from LJC that went the hard way last week and
found this workaround for me
_______________________________________________
forge-dev mailing list
forge-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/forge-dev