# 使用 Homebrew 安装 openliberty-jakartaee9 查看 openliberty-jakartaee9 的安装路径、可执行文件、元数据以及面向 AI 代理工作流的安全说明。 ## 安装 ```sh sudo av install brew:openliberty-jakartaee9 ``` 其他安装命令: ### macOS - Homebrew (100%): ```sh brew install openliberty-jakartaee9 ``` 证据: local Homebrew formula metadata ## 软件包事实 - **软件包键:** brew:openliberty-jakartaee9 - **软件包管理器:** Homebrew - **版本:** 23.0.0.2 - **来源摘要:** Lightweight open framework for Java (Jakarta EE 9) - **主页:** - **最后更新:** 2026-07-30T10:53:33+09:00 - **已生成:** 2026-08-03T19:37:03+00:00 ## 可执行文件 - openliberty-jakartaee9 (别名) ## 安装行为 - Bottle: 不可用 ## 版本和新鲜度 - 页面生成时间: 2026-08-03 - 管理器版本: 23.0.0.2 ## 项目历史与用法 openliberty-jakartaee9 is the Homebrew Open Liberty package for the Jakarta EE 9 line, represented in Open Liberty documentation by the Jakarta EE 9.1 platform feature. It packages IBM's open source Liberty runtime around the Jakarta namespace transition, the release family where enterprise Java APIs moved from `javax.*` to `jakarta.*`. ### 项目历史 Open Liberty descends from IBM Liberty, created in 2012 for a smaller, modular application-server model and released as open source in 2017. The project became IBM's public development base for a runtime that implements Jakarta EE and MicroProfile while also underpinning WebSphere Liberty. Jakarta EE 9 and 9.1 were historically significant because they changed the package namespace from `javax` to `jakarta`. Open Liberty tracked that shift in its features: the Jakarta EE 9.1 platform feature combines the Liberty features for the full platform and uses `jakartaee-9.1` in server configuration. ### 采用历史 Open Liberty was part of the Jakarta EE 9.1 ratification story: the project stated that its beta was compatible with both the Jakarta EE 9.1 Web Profile and Platform specifications using Java SE 8 and Java SE 11. That positioned Liberty as an early implementation for teams testing the namespace migration before larger fleet moves. The package's adoption role is therefore migration-oriented. It gives developers a packaged runtime for validating applications, build pipelines, and server.xml feature configuration against the Jakarta EE 9 generation rather than the Java EE 8/Jakarta EE 8 compatibility line. ### 使用方式 A developer selecting this package is usually dealing with applications or libraries that have moved to the `jakarta.*` APIs. In Open Liberty, enabling the platform pulls in the Jakarta EE Web Profile plus full-platform components such as connectors, messaging, mail, XML binding, XML web services, and application-client support. The broader Open Liberty workflow supports Maven, Gradle, Docker, and IDE tooling, but the Homebrew formula provides a simple package-manager route for local testing and operations scripts that expect a named runtime package. ### 为什么软件包爱好者会关心 openliberty-jakartaee9 is a clean example of a package name carrying standards-version semantics. The distinction from openliberty-jakartaee8 is not cosmetic: Jakarta EE 9 is the namespace migration line, so package catalogs need to treat it as a different compatibility target. It also shows why runtime packages for Java servers can age differently from the upstream project. A formula may be preserved to serve a standards line even while Open Liberty itself keeps releasing newer Jakarta EE platform levels. ### 时间线 - 2012: IBM Liberty was created as a small-footprint Java runtime. - 2017: IBM released the Liberty source as Open Liberty. - 2020: Open Liberty public beta work exposed early Jakarta EE 9 features. - 2021: Open Liberty announced Jakarta EE 9.1 beta compatibility for both Web Profile and Platform on Java SE 8 and Java SE 11. - Open Liberty documentation defines `jakartaee-9.1` as the full Jakarta EE 9.1 Platform convenience feature. ### Related projects - Related projects include Jakarta EE 9.1, the Eclipse Transformer migration tooling, WebSphere Liberty, Open Liberty Web Profile 9, and Open Liberty's Maven, Gradle, and container-image distribution paths. ### 来源 - - - - - - ## 安全说明 narrow executable package without higher-risk signals. - **Geiger 风险:** 绿色 / 低 - narrow executable package without higher-risk signals ## 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-jakartaee9.yml](https://github.com/mxcl/pkgdb/blob/main/combined/openliberty-jakartaee9.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