# 使用 Homebrew 安装 openliberty-microprofile4 查看 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 的匹配本地密钥处理 manifest。Nucleus 软件包元数据仍在此发布，以便未来覆盖拥有稳定的软件包 URL。 ## 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