openliberty-microprofile4 を Homebrew でインストール

プロジェクトリンク

• ホームページ

コマンドとエイリアス

• openliberty-microprofile4

プロジェクトの歴史

Open Liberty was open sourced by IBM in 2017 from Liberty, a runtime IBM started in 2012 for small footprint, modular configuration, and flexible Java deployment. The project has since acted as IBM's open implementation base for Jakarta EE and Eclipse MicroProfile and as the foundation for WebSphere Liberty.

MicroProfile emerged to standardize APIs common in Java microservices. Open Liberty's `microProfile-4.0` feature combines Liberty support for Eclipse MicroProfile 4.0 for Cloud Native Java and includes capabilities such as Config 2.0, Fault Tolerance 3.0, Health 3.0, Metrics 3.0, OpenAPI 2.0, OpenTracing 2.0, and Rest Client 2.0.

採用の歴史

Open Liberty has long used MicroProfile as part of its cloud-native positioning: enterprise Java teams could run a smaller set of service-oriented APIs without enabling a whole Jakarta EE platform. MicroProfile 4.0 aligned with Jakarta EE 8, which made it a useful bridge for organizations already standardized on Java EE 8 APIs while adopting microservice conventions.

A MicroProfile-specific package is attractive to developers and operators who care about the exact API bundle available on disk. It separates the microservice profile from Open Liberty's Jakarta EE full-platform and Web Profile packages.

使われ方

In a Liberty server, the MicroProfile 4.0 convenience feature is enabled with `<feature>microProfile-4.0</feature>` in `server.xml`. That enables CDI, JAX-RS, JSON-B, JSON-P, Servlet, and the MicroProfile APIs used for externalized configuration, health endpoints, metrics, OpenAPI descriptions, fault tolerance, tracing, JWT, and REST clients.

Developers use this runtime for local service development, CI checks, and deployment packaging where the application expects MicroProfile 4 behavior. The same Open Liberty ecosystem also offers Maven and Gradle plugins, container images, and IDE tooling for iterative dev mode.

パッケージ好きにとっての重要性

This formula is notable because it tracks an API profile, not just an upstream release train. Package managers that expose Open Liberty by MicroProfile level let users install a runtime whose compatibility promise is visible in the package name.

It also captures the enterprise Java split between platform profiles and microservice profiles: `openliberty-microprofile4` overlaps with Jakarta EE components but exists for a different operational story.

タイムライン

• 2012: Liberty began inside IBM as a lightweight runtime.
• 2017: IBM opened Liberty development as Open Liberty on GitHub.
• 2021: MicroProfile 4.0 aligned with Jakarta EE 8 and was documented in Open Liberty tutorials and feature references.
• Open Liberty documentation defines `microProfile-4.0` as the convenience feature for Eclipse MicroProfile 4.0 for Cloud Native Java.

Related projects

• Related technologies include Eclipse MicroProfile, Jakarta EE 8, Open Liberty's MicroProfile feature family, WebSphere Liberty, and the Open Liberty Maven and Gradle plugins.

ソース

• https://formulae.brew.sh/formula/openliberty-microprofile4
• https://github.com/openliberty
• https://microprofile.io/2021/04/12/a-deep-dive-into-microprofile-4-0-with-open-liberty/
• https://openliberty.io/blog/2022/09/21/history-maker-projects.html
• https://openliberty.io/docs/latest/reference/feature/microProfile-4.0.html
• https://openliberty.io/start/