Drop your Maven project folder here (or click to choose it)
How to use
How to use it
Open your project folder (or paste a pom.xml) and type the command you would run. You get every phase that command goes through, with the goals that run in it and where each one comes from: what Maven binds by default for the packaging, your pom, the parent or a profile. Click a goal to see its origin and its line in the pom.
How much can I trust it?
The result has been checked goal by goal against what Maven really prints (3.10 and 4.0) in eleven cases: Spring Boot, multi-module, WAR, Quarkus, Micronaut, Apache Commons, -pl -am, verify and standalone goals. What it cannot know (a parent of yours you haven't opened, a plugin it doesn't know) it does not make up: it tells you.
Pom review and Gradle
The pom review warns about what breaks or changes the build when moving to Maven 3.10 or 4 (a duplicated plugin or dependency now stops the build; a plugin without a version changes on its own), and about versions repeated across modules. All of it measured against real Maven. With Gradle the build.gradle cannot be read, because it is code: paste the output of ./gradlew build --dry-run and you get the real task order, with each task's Maven equivalent.
Plugin and parent data
The default phase of each goal and what the usual parents (Spring Boot, Apache, Micronaut, JBoss…) add come from Maven Central, which cannot be queried from the browser. They ship with the tool, dated 2026-10-25. If your parent is newer, the closest one is used and you are told.
