# tomee-plume を Homebrew でインストール
tomee-plume のインストール経路、実行ファイル、メタデータ、AI エージェント向けセキュリティノートを確認します。
## インストール
```sh
sudo av install brew:tomee-plume
```
追加のインストールコマンド:
### macOS
- Homebrew (100%):
```sh
brew install tomee-plume
```
証拠: local Homebrew formula metadata
## パッケージ情報
- **パッケージキー:** brew:tomee-plume
- **パッケージマネージャ:** Homebrew
- **バージョン:** 10.2.0
- **ソース概要:** Apache TomEE Plume
- **ホームページ:**
- **最終更新:** 2026-07-17T17:13:42Z
- **生成日時:** 2026-08-03T19:37:03+00:00
## 実行可能ファイル
- catalina.sh (エイリアス)
- ciphers.sh (エイリアス)
- configtest.sh (エイリアス)
- daemon.sh (エイリアス)
- digest.sh (エイリアス)
- makebase.sh (エイリアス)
- migrate.sh (エイリアス)
- setclasspath.sh (エイリアス)
- shutdown.sh (エイリアス)
- startup.sh (エイリアス)
- tomee.sh (エイリアス)
- tool-wrapper.sh (エイリアス)
- version.sh (エイリアス)
## インストール挙動
- Bottle: 利用不可
## バージョンと鮮度
- ページ生成日: 2026-08-03
- マネージャ版: 10.2.0
## プロジェクトの歴史と使われ方
Apache TomEE Plume is the broadest traditional TomEE flavor, packaging Tomcat with TomEE Plus capabilities and extra JSF/JPA implementation choices. Its history is inseparable from TomEE's attempt to keep the Tomcat operating model while adding Java EE and Jakarta EE application-server services.
### プロジェクトの歴史
TomEE grew out of Apache OpenEJB work. An Apache presentation traces OpenEJB from its 1999 origins through incubation, graduation, and 2011 integration into Apache TomEE. TomEE's own pages describe the product as a Tomcat-based server assembled by starting with a vanilla Tomcat zip, adding TomEE jars, and repackaging the result.
The Plume flavor appeared in the TomEE 1.7.0 feature release as an experimental profile. The release notes described it as TomEE Plus with Mojarra and EclipseLink added, explicitly positioning it as a lower-friction path for users coming from GlassFish-style environments.
### 採用の歴史
TomEE 1.x passed the Java EE 6 TCK, making Web Profile certification part of the project's early adoption story. Plume itself was marked not certified in the old 1.7.4 download page, but it served users who wanted the broader Plus feature set plus familiar JSF and JPA implementations.
In the package-manager niche, a separate tomee-plume formula is useful because TomEE flavors are shipped as different binary distributions rather than one runtime toggled by a small config flag.
### 使われ方
Package users choose Plume when they want a Tomcat-like layout and scripts but expect more of the full application-server stack out of the box, especially the Plus profile plus Mojarra and EclipseLink support.
### パッケージ好きにとっての重要性
Plume is interesting to package maintainers because it is a distribution flavor, not merely an optional dependency. Keeping it as a distinct formula lets users install the heavier TomEE bundle intentionally and keeps lighter WebProfile installations smaller.
### タイムライン
- 1999: OpenEJB originated before its later Apache history.
- 2011: OpenEJB was integrated into Apache TomEE.
- TomEE 1.7.0: Introduced the Plume profile with Mojarra and EclipseLink.
- 2016: TomEE 1.7.4 listed Web Profile, JAX-RS, Plus, and Plume downloads as separate distributions.
### Related projects
- Apache Tomcat is the base runtime TomEE extends.
- Apache TomEE Plus is the flavor Plume builds on.
- Mojarra and EclipseLink are the extra implementation choices called out by the Plume release notes.
### ソース
-
-
-
-
-
- input.source_facts.package-manager
## セキュリティノート
narrow executable package without higher-risk signals.
- **Geiger リスク:** グリーン / 低
- narrow executable package without higher-risk signals
## Combined YAML source
View the package source record on GitHub. [combined/tomee-plume.yml](https://github.com/mxcl/pkgdb/blob/main/combined/tomee-plume.yml)
## ソース
- pkg.so package database
- Geiger risk classifier
- curated package history
- pkgdb category and tag curation
- cross-ecosystem install command graph