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@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@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/forge-dev

_______________________________________________
forge-dev mailing list
forge-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/forge-dev