Maven core extension

Machine-readable Maven output.
Structured failure details.

A Maven core extension that suppresses most default lifecycle logging when activated and emits compact output with build status, test results, and compiler diagnostics.

Before & after

Standard Maven (excerpt)
[INFO] Scanning for projects...
[INFO] --------
[INFO] Reactor Build Order:
[INFO]
[INFO]   my-parent
[INFO]   my-core
[INFO]   my-api
[INFO]   my-web
[INFO]
[INFO] --------
[INFO] Building my-core 1.0
[INFO] --------
[INFO]
[INFO] --- maven-clean-plugin:3.2.0:clean ---
[INFO] Deleting /home/user/project/target
[INFO]
[INFO] --- maven-resources-plugin:3.3.0 ---
[INFO] Copying 3 resources
[INFO]
[INFO] --- maven-compiler-plugin:3.11.0 ---
[INFO] Compiling 42 source files
[INFO]
[INFO] --- maven-surefire-plugin:3.1.2 ---
[INFO] Using auto detected provider
[INFO] -------------------------------------------------------
[INFO]  T E S T S
[INFO] -------------------------------------------------------
[INFO] Running com.example.AppTest
...
... 60+ more lines of this ...
...
With MSE (success summary example)
MSE:SESSION_START modules=4 goals=clean,verify
MSE:OK modules=4 passed=342 failed=0 errors=0 skipped=0 time=47s

What MSE does

Behavior summary for Maven 3.6.x to 3.9.x.

>_

Machine-readable output

Primary status lines use the MSE: prefix with key=value fields, which makes them easy to parse in tools and scripts.

#!

Compact success output

Successful builds emit a compact summary instead of full lifecycle logs. Exact output size depends on the build and enabled outputs.

</>

Structured failures

Test failures include class, method, message, and stack trace lines. Compiler failures include file path, line, and column when parseable.

Surefire/Failsafe reports

Reads Surefire and Failsafe XML reports from module target directories, including runs that fork test JVMs and still write XML results.

Activation

Pass -Dmse or set MSE_ACTIVE=true. Without activation, Maven behavior is unchanged.


Install and run

Works with Java 11+ and Maven 3.6.x to 3.9.x

1

Install the extension

Run the installer plugin in your project root. It creates .mvn/extensions.xml automatically.

$ mvn info.jerrinot:mse-maven-plugin:install
2

Run your build with MSE

Activate with a system property:

$ mvn -Dmse clean verify

Or with an environment variable:

$ MSE_ACTIVE=true mvn clean verify
3

Uninstall (if needed)

Clean removal with a single command.

$ mvn info.jerrinot:mse-maven-plugin:uninstall

Note: This project came out of frustration with Maven logs polluting LLM context during coding sessions. The author does not claim deep Maven internals expertise, and parts were frankly vibe-coded. It appears to work and aims to reduce noise, but treat it as an attempt to mitigate the problem, not a formal guarantee. Use at your own risk, and bug reports are very much appreciated.