3:08 a.m.
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?
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
3:55 a.m.
----- 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
6:06 a.m.
Hi Ivan,
This is still not fixed in later versions of JDK8.
JDK 1.8.0_11 is the last JDK version where forge builds/runs.
I guess one option is that we'll have to make our services derived from the simple
service NOT implement the Service interface. This is not required atm, but the javadoc
says that it is possible.
However, I think we might run in runtime issues when the addon boots up due to lacking
dependencies. That's all I remember from working in this issue
Em 26/11/2014, às 07:09, Ivan St. Ivanov
<ivan.st.ivanov(a)gmail.com> escreveu:
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?
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
1:09 p.m.
Hi George,
While reading the JIRA again and again it seems that this is a feature, not
a bug in javac. So it will be here to stay. Which means that it is us that
have to think about a solution. Probably that is why the issue is still
open :)
Cheers,
Ivan
On Wed, Nov 26, 2014 at 2:06 PM, George Gastaldi <ggastald(a)redhat.com>
wrote:
Hi Ivan,
This is still not fixed in later versions of JDK8.
JDK 1.8.0_11 is the last JDK version where forge builds/runs.
I guess one option is that we'll have to make our services derived from
the simple service NOT implement the Service interface. This is not
required atm, but the javadoc says that it is possible.
However, I think we might run in runtime issues when the addon boots up
due to lacking dependencies. That's all I remember from working in this
issue
Em 26/11/2014, às 07:09, Ivan St. Ivanov <ivan.st.ivanov(a)gmail.com>
escreveu:
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?
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
_______________________________________________
forge-dev mailing list
forge-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/forge-dev
1:12 p.m.
Hi Ivan,
Good call, I changed it to "New Feature".
Thanks for pointing that out.
Best Regards,
George Gastaldi
On 11/26/2014 05:09 PM, Ivan St. Ivanov wrote:
Hi George,
While reading the JIRA again and again it seems that this is a
feature, not a bug in javac. So it will be here to stay. Which means
that it is us that have to think about a solution. Probably that is
why the issue is still open :)
Cheers,
Ivan
On Wed, Nov 26, 2014 at 2:06 PM, George Gastaldi <ggastald(a)redhat.com
<mailto:ggastald@redhat.com>> wrote:
Hi Ivan,
This is still not fixed in later versions of JDK8.
JDK 1.8.0_11 is the last JDK version where forge builds/runs.
I guess one option is that we'll have to make our services derived
from the simple service NOT implement the Service interface. This
is not required atm, but the javadoc says that it is possible.
However, I think we might run in runtime issues when the addon
boots up due to lacking dependencies. That's all I remember from
working in this issue
Em 26/11/2014, às 07:09, Ivan St. Ivanov <ivan.st.ivanov(a)gmail.com
<mailto:ivan.st.ivanov@gmail.com>> escreveu:
> 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?
>
> 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 <mailto:forge-dev@lists.jboss.org>
> https://lists.jboss.org/mailman/listinfo/forge-dev
_______________________________________________
forge-dev mailing list
forge-dev(a)lists.jboss.org <mailto:forge-dev@lists.jboss.org>
https://lists.jboss.org/mailman/listinfo/forge-dev
_______________________________________________
forge-dev mailing list
forge-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/forge-dev
3660
days inactive
3660
days old
4 comments
3 participants
participants (3)
-
George Gastaldi -
Ivan St. Ivanov -
Vineet Reynolds Pereira