# openliberty-microprofile4 を Homebrew でインストール openliberty-microprofile4 のインストール経路、実行ファイル、メタデータ、AI エージェント向けセキュリティノートを確認します。 ## インストール ```sh sudo av install brew:openliberty-microprofile4 ``` 追加のインストールコマンド: ### macOS - Homebrew (100%): ```sh brew install openliberty-microprofile4 ``` 証拠: local Homebrew formula metadata ## パッケージ情報 - **パッケージキー:** brew:openliberty-microprofile4 - **パッケージマネージャ:** Homebrew - **バージョン:** 26.0.0.7 - **ソース概要:** Lightweight open framework for Java (Micro Profile 4) - **ホームページ:** - **最終更新:** 2026-07-30T10:53:33+09:00 - **生成日時:** 2026-08-03T19:37:03+00:00 ## 実行可能ファイル - openliberty-microprofile4 (エイリアス) ## インストール挙動 - Bottle: 利用不可 ## バージョンと鮮度 - ページ生成日: 2026-08-03 - マネージャ版: 26.0.0.7 ## プロジェクトの歴史と使われ方 openliberty-microprofile4 is the Homebrew Open Liberty distribution aimed at Eclipse MicroProfile 4.0 workloads. It packages the same Open Liberty runtime lineage around the MicroProfile API set for cloud-native Java services rather than around the full Jakarta EE platform. ### プロジェクトの歴史 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 `microProfile-4.0` 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. ### ソース - - - - - - ## セキュリティノート openliberty-microprofile4 に一致するローカルシークレット処理マニフェストは見つかりませんでした。将来の対応で安定したパッケージ URL を使えるよう、Nucleus パッケージメタデータはここに公開されています。 ## Configuration and credential file locations These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval. ## Configuration files - Unix: ${wlp.user.dir}/servers/${wlp.server.name}/server.xml, ${wlp.user.dir}/servers/${wlp.server.name}/bootstrap.properties, ${wlp.user.dir}/servers/${wlp.server.name}/server.env, ${wlp.user.dir}/servers/${wlp.server.name}/jvm.options ## Combined YAML source View the package source record on GitHub. [combined/openliberty-microprofile4.yml](https://github.com/mxcl/pkgdb/blob/main/combined/openliberty-microprofile4.yml) ## ソース - pkg.so package database - Geiger risk classifier - curated configuration and credential file locations - curated package history - pkgdb category and tag curation - cross-ecosystem install command graph