[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [ee4j-community] Eclipse is still behind the current state of Java EE 8
|
With things moving to Eclipse, it would definitely be very beneficial for the IDE to start having much better support for Java EE. This is key to the success of EE4J. Hopefully major vendors already recognize this? Needing to install JBoss tools on top of Eclipse just for better Java EE support has always felt cumbersome.
Sent via the Samsung Galaxy S7, an AT&T 4G LTE smartphone
-------- Original message --------
From: arjan tijms <arjan.tijms@xxxxxxxxx>
Date: 2/25/18 8:58 AM (GMT-05:00)
To: EE4J community discussions <ee4j-community@xxxxxxxxxxx>
Subject: Re: [ee4j-community] Eclipse is still behind the current state of Java EE 8
Hi,
This is indeed an issue. For JSF 2.3 another issue is that it actually throws an exception when a faces config with version 2.3 is used, despite JSF 2.3 now being almost a year old.
I wonder if Red Hat would be open to contribute its JSF (RichFaces) tooling to WTP. This is somewhat ahead of WTP, and JSF/RichFaces is likely not that important to Red Hat anymore (RichFaces was EOL'd a while back).
Locally I've been working on the last published version of GlassFish tools a little, adding a small extra feature (the ability to just choose the home directory where GF/Payara is installed, and not having to choose one of the internal folders). I'm now 'fairly' up to date with the code to be able to add some other features I had planned.
Of course, there's much more needed, especially indeed bringing everything up to date with Java EE 8, and then EE4J/Jakarta EE.
Kind regards,
Arjan Tijms
