Payara Micro provides build tool plugins for Maven and Gradle. The plugins allows to start/stop/reload Payara Micro instance and package uber jar bundle of application. To illustrate the use of Payara Micro Maven Plugin, I'll be revisiting my earlier blog on another feature of Payara Micro - the ability to use Payara Micro as a JMS consumer.

Eclipse MicroProfile es una especificación para un conjunto de APIs diseñadas para construir MicroServicios. Este proyecto ha existido desde hace más de un año y es algo con lo que Payara está altamente comprometido. Los lectores a los que les gusta estar al día con las noticias desde a comunidad de Java probablemente serán conscientes de como el proyecto ha progresado a grandes saltos últimamente. Está siendo un camino largo y arduo desde la versión 1.0 a la versión 1.1 de la especificación pero, en este momento, mucho ha sido desarrollado y hay multitud de APIs actualmente en desarrollo.

See here for the original version in English language.  

The Eclipse MicroProfile is a specification for a set of APIs appropriate to building MicroServices. The project has existed for over a year now and is something that Payara is highly committed to. Readers who like to keep up-to-date with news from the Java community will probably already be aware of how the project has progressed in leaps and bounds lately. It's been a long road from version 1.0 to version 1.1 of the specification but, in that time, a lot has developed and there are multiple APIs currently being worked on.

Read this post in Spanish.

In the last few weeks, we have released two builds of Payara Server; our new major version 172 and third patch build of version 171 - 171.3. This is the first time we've ever released two distinct builds in the same month, so why are we doing it?

Payara Server 171 was a huge release with lots of new features and improvements on many others. We've already written about improvements to the Request Tracing service and had a guest blog about using the email notifier.

The email notifier is just one of a whole host of notifiers we now have available. A lot were added in the 171 release and more are on their way in the imminent 172 release!

The capability to disable implicit CDI scanning was already added to the previous Payara Server releases but the default admin console setting was to enable it at deploy time. We have now made a change so that the value added to the deployment descriptor is the overriding setting and the admin console setting will be ignored.

For even more control, we have added the ability to explicitly include or exclude JARs within an Application Deployment from CDI scanning. You can now, for example, include all JARs by default and exclude some named ones, or do the opposite and exclude all by default and only include some named ones.

2016 has been a bit of a wild ride, to say the least. Lots of major things have happened politically and in popular culture. Considering the world of Java and its related ecosystems, we've seen a lot of activity too, with announcements about the delay of Java 9, the concerns raised by the Java EE Guardians (shared by many), and a largely unprecedented move in the establishment of the MicroProfile initiative.