After two decades as Java's dominant build tool (no offense to Gradle), Maven is undergoing its most significant evolution. While the official Maven documentation outlines the technical changes in Maven 4, this blog post focuses specifically on what these changes mean for enterprise developers working with Jakarta EE, Spring Boot and Quarkus.

As a Java developer, you've probably experienced the challenges of deploying Jakarta EE or MicroProfile applications to the cloud. Setting up infrastructure, configuring servers and dealing with the gamut of cloud environments can be a major deviation from your core development tasks, ultimately influencing your productivity. However, there are tools that you can leverage to simplify and streamline cloud deployments. One is Payara Cloud Maven plugin - let's look at what it offers and how to use it in this blog post.

Maven is arguably the most used build automation tool in the Java ecosystem. With that great power and popularity, comes great...configuration options! One such option that can leave you scratching your head is dependency scopes. This blog post takes a quick look at maven scopes, what they are and when to choose which scope.

Introduction

Payara Micro, a lightweight and flexible microservices runtime platform, offers a seamless development experience through its Maven plugin. In this guide, we'll explore the Dev Mode of Payara Micro Maven plugin, focusing on the dev goal. This goal is tailored to streamline development by enabling various features for an efficient workflow.

Development productivity is crucial in Enterprise Java and Jakarta EE application development, supporting the delivery of high-quality software solutions quickly and efficiently. As a result, it is necessary to focus on streamlining development processes, optimizing resource utilization and empowering developers to work more effectively. Payara Micro Maven Plugin, Version 1, introduces a powerful tool – Dev Mode – designed to supercharge your development experience with Payara Micro. 

In our latest User Guide - available to download here - we look at this plugin, exploring its features, configurations and usage to help developers unlock stratospheric levels of productivity.

One of the most daunting tasks organizations face is keeping pace with fast evolving technological landscapes, while ensuring existing applications remain robust and functional. If you're still running applications on Java EE 7/8,  the release of Jakarta EE 10 sets the upgrade clock ticking. Of course you can keep running such applications with a Payara Enterprise 5 plan. However, if you need to upgrade to take advantage of the many new features in Jakarta EE 10, then read on!

Payara Microでは、Webアプリケーションを自己完結型で簡単に実行することができます。2016年5月のPayara Serverリリースからは、WARファイルの内容とPayara Microを構成するクラスやリソースを束ねる “Uber JAR” を作成する簡単な方法があります。

この “Uber” Jarは、Dockerコンテナ内でアプリケーションを実行するための最良の方法ではないことに注意してください。アプリケーションに小さなコード変更を加えるたびに、バイナリ全体のアップデートが必要になるためです。より良い方法は、Payara Microインスタンスを起動して、インストールが必要なアプリケーションを指定することです。詳細については Payara Micro Docker Image documentation をご覧ください。

(最終更新日 2021/04/06)

Did You Know?

Payara Server上でアプリをテストする時、IDEと連携してアプリをテストできるようにしておくと非常に便利です (そもそも、そのためのIDEですが)。もしNetBeansを使用しているのなら非常に簡単に実現できます。このブログではPayara ServerをNetBeansにセットアップしてWebアプリを実行するための手順をご紹介します。

Cuando estás probando una aplicación para ejecutarla en Payara Server, continuamente probar la aplicación desde tu IDE es extremadamente util (ese es su proposito, despues de todo). Si estás utilizando NetBeans esto es muy sencillo. Sigue los pasos de este blog para configurar Payara Server en NetBeans para ejecutar tus aplicaciones web.