# Install tomee-plus with Homebrew

Everything in TomEE Web Profile and JAX-RS, plus more. Version 10.2.0 via Homebrew; verified 2026-07-17.

## Install

```sh
sudo av install brew:tomee-plus
```

Additional install commands:

### macOS

- Homebrew (100%):

```sh
brew install tomee-plus
```

  Evidence: local Homebrew formula metadata

## Package facts

- **Package key:** brew:tomee-plus
- **Package manager:** Homebrew
- **Version:** 10.2.0
- **Source summary:** Everything in TomEE Web Profile and JAX-RS, plus more
- **Homepage:** <https://tomee.apache.org/>
- **Last updated:** 2026-07-17T17:13:57Z
- **Generated:** 2026-08-03T19:37:03+00:00

## Executables

- tomee-plus-startup (alias)

## Install behavior

- Bottle: not available

## Freshness

- Page generated: 2026-08-03
- Package-manager version: 10.2.0
## Project history and usage

Apache TomEE Plus is the TomEE distribution for users who want Tomcat's operational shape with a broader Java EE and Jakarta EE feature set than WebProfile. It is packaged separately because the extra APIs and implementations materially change the runtime footprint.

### Project history

TomEE's design is to begin with Apache Tomcat, add TomEE jars, and ship the result as Tomcat plus enterprise features. That design followed the OpenEJB lineage: ASF presentation material records OpenEJB's 2011 integration into TomEE after earlier moves through SourceForge, Apache Geronimo, Codehaus, the Apache Incubator, and Apache OpenEJB graduation.

The Plus flavor was already present in the TomEE 1.0.0 beta-1 downloads in 2011, where Web Profile artifacts were listed as Java EE 6 certified and Plus artifacts as not certified. Later TomEE pages summarized Plus as Web Profile and JAX-RS plus EJB Full, Java EE Connector Architecture, JMS, and JAX-WS.

### Adoption history

TomEE appealed to Tomcat users who wanted Java EE services without switching to a larger traditional application server. Plus served the subset that needed the fuller service surface, especially messaging, connector architecture, and web services APIs.

For Homebrew-style packaging, tomee-plus exposes that heavier TomEE distribution as a clear install target. The package gives Java developers a repeatable local runtime for projects that are beyond Web Profile but still expect Tomcat-like startup scripts and directory layout.

### How it is used

Developers install TomEE Plus when testing or running applications that need JAX-RS plus additional enterprise services such as JMS, JAX-WS, EJB Full, or connector support. It is used like a Tomcat distribution, with TomEE-provided startup wrappers and the familiar catalina-based tooling.

### Why package nerds care

The formula boundary matters because Plus is not just TomEE with a runtime flag. It selects a fuller binary flavor, so package catalogs can keep WebProfile, Plus, and Plume users from accidentally installing the wrong server surface.

### Timeline

- 1999: OpenEJB began as an EJB container project.
- 2011: OpenEJB was integrated into Apache TomEE.
- 2011: TomEE 1.0.0 beta-1 downloads included a Plus distribution.
- 2016: TomEE 1.7.4 described Plus as Web Profile and JAX-RS plus EJB Full, connector architecture, JMS, and JAX-WS.

### Related projects

- Apache TomEE WebProfile is the smaller TomEE flavor below Plus.
- Apache TomEE Plume builds on Plus by adding Mojarra and EclipseLink support.
- Apache Tomcat is the base server distribution TomEE extends.

### Sources

- <https://tomee.apache.org/>
- <https://tomee.apache.org/index.old.html>
- <https://tomee.apache.org/presentations/2011_JAX_London_Fun_EJB31_and_OpenEJB.pdf>
- <https://tomee.apache.org/refcard/refcard.html>
- <https://tomee.apache.org/tomee-1.0.0-beta-1.html>
- input.source_facts.package-manager


## Security Notes

narrow executable package without higher-risk signals.

- **Geiger risk:** green / low
- narrow executable package without higher-risk signals


## Combined YAML source

View the package source record on GitHub. [combined/tomee-plus.yml](https://github.com/mxcl/pkgdb/blob/main/combined/tomee-plus.yml)


## Sources

- pkg.so package database
- Geiger risk classifier
- curated package history
- pkgdb category and tag curation
- cross-ecosystem install command graph