Ankündigung im Blog https://spring.io/blog/2019/09/30/spring-framework-5-2-goes-ga:
Spring Framework 5.2 requires JDK 8 or higher and specifically supports JDK 11 as the current long-term support branch as well as JDK 13 as the latest OpenJDK release. It comes with many performance improvements (affecting startup time as well as peak performance) and further steps taken towards GraalVM native image support.
This release deeply integrates with Kotlin 1.3 and provides first-class support for Kotlin coroutines on top of Spring WebFlux. Furthermore, it comes with reactive messaging integration for the RSocket protocol as well as reactive transaction management for R2DBC, MongoDB and Neo4j (with datastore integration provided by Spring Data’s modules).
As of the upcoming Spring Boot 2.2 RC1 release, you’ll be able to consume Spring Framework 5.2 GA through start.spring.io!
Details siehe https://github.com/spring-projects/spring-boot/releases/tag/v2.1.4.RELEASE
Auch Spring Boot 2.2 kommt einen Schritt weiter richtig GA.
Einen Tag vor Java 12 wurde PrimeFaces 7 freigegeben. Details unter https://www.primefaces.org/primefaces-7-0-final-released/
Die Doku ist mittlerweile bei GitHub: https://primefaces.github.io/primefaces/7_0_0/#/
Download unter https://projects.eclipse.org/projects/ee4j.glassfish/downloads
Eclipse GlassFish is a complete application server that implements the Jakarta EE specification. GlassFish includes implementations of all required and optional Jakarta EE APIs, and passes all Jakarta EE TCKs. GlassFish also includes a complete administration console, clustering support, and other developer and production focused tools and features.
Siehe http://wildfly.org/news/2018/12/13/WildFly15-Final-Released/. Läuft ordentlich auf Java 11. Zur Wiederholung der Versionen:
JBoss 3.2.x. implementiert Java EE-Spezifikation 1.3(.1) (EJB 2.0)
JBoss 4.x: Java EE 1.4 (EJB 2.1, Servlet 2.4, JSF 2.1, …) und am Ende der Serie schon Teile von Java EE 5.
JBoss 5.x: Java EE 5 (EJB 3, JPA 1.0, Servlet 2.5, JSP 1.2)
JBoss 6.x: Java EE 6 (EJB 3.1, CDI 1.0, JPA 2.0, Servlet 3.0, JSF 2.0, JAX-WS 2.2, JAX-RS 1.1, Bean Validation 1.0)
JBoss 7.x: ebenfalls Java EE 6. Implementierung hat modularen Kernel, neue Verzeichnisstruktur.
Wildfly 8.x Java EE 7 zertifiziert für Voll- und Web-Profil. Vierteljährliche Updates.
Wildfly 14.x. Java EE 8 zertifiziert
Wildfly 15. Aktuellste Version, läuft gut auf Java 11
So schreibt es https://github.com/Netflix/Hystrix:
Hystrix is no longer in active development, and is currently in maintenance mode.
Hystrix (at version 1.5.18) is stable enough to meet the needs of Netflix for our existing applications. Meanwhile, our focus has shifted towards more adaptive implementations that react to an application’s real time performance rather than pre-configured settings (for example, through adaptive concurrency limits). For the cases where something like Hystrix makes sense, we intend to continue using Hystrix for existing applications, and to leverage open and active projects like resilience4j for new internal projects. We are beginning to recommend others do the same.
Netflix Hystrix is now officially in maintenance mode, with the following expectations to the greater community: Netflix will no longer actively review issues, merge pull-requests, and release new versions of Hystrix. We have made a final release of Hystrix (1.5.18) per issue 1891 so that the latest version in Maven Central is aligned with the last known stable version used internally at Netflix (1.5.11). If members of the community are interested in taking ownership of Hystrix and moving it back into active mode, please reach out to firstname.lastname@example.org.
So schreibt es das Unternehmen auf dem Blog: https://blog.github.com/2018-11-15-state-of-the-octoverse-top-programming-languages/.
Top programming languages by repositories created, 2008-2018
Top programming languages by contributor as of September 30, 2018
Details im Wildfly-Blog http://wildfly.org/news/2018/05/30/WildFly13-Final-Released
Standardmäßig startet der Container noch im EE 7 Modus.
Siehe https://spring.io/blog/2018/04/16/spring-tool-suite-3-9-4-released und https://docs.spring.io/sts/nan/v394/NewAndNoteworthy.html
Basiert nun auf Eclipse Oxygen.3a, womit Java 10 möglich wird.
Supports running in Java 9. Note that this does not yet mean that GWT can compile Java 9 sources, or support the Java 9 JRE changes, but that a Java 9 JRE can be used to compile a GWT project. Do note that the new
--module-path flag is not supported, but
-classpath must still be used as in the past.
Chrome 61 removed functionality that had been used for reading the absolute top/left values. The internal implementation has been updated to reflect modern standards.
Uncaught exception handler will now receive all errors on the page, as handled by
window.onerror. This may potentially be a breaking change if there were misbehaving scripts on the page. To disable this functionality, set the property
<set-property name="gwt.uncaughtexceptionhandler.windowonerror" value="IGNORE"/>
For more details, see
- LookupMethodCreator creates too large method
- NativeRegExp should use iframe instance, fixing Edge JIT bug
- JsProperty getter/setter sometimes were reported as incompatible
- Instantiating native JsTypes from JSNI results in InternalCompilerException
- Remove the SUBSIZED characteristic from filtered streams
- Internal compiler exception when using native JsType varargs in a JsMethod
- Regression in String.toLowerCase and toUpperCase for some locales, specifically for Turkish
- Missing bounds check in String.charAt
- Fix AIOOBE when compiling method references involving varargs.
- Apply HtmlUnit workaround ensuring that window.onerror is called correctly
- Migrated lang/jre emulation JSNI to JsInterop to share with J2CL
- Added ErrorProne to gwt builds
- Improved compliance with CSP
- Added emulation for java.io.Externalizable
- Added emulation for java.lang.reflect.Array
- JSO.equals/hashcode will delegate to the JS object if it has methods with those names
- Removed outdated or unused parts of project
- Migrate guava JRE emulation to GWT
- HtmlUnit tests are now run in batch mode
For more detail, see the issue tracker and the commit log.
Alle Details auf der schön gemachten Webseite http://junit.org/junit5/.