Apache Maven

Maven online pom.xml in, running code out

A real Apache Maven build in the cloud: edit pom.xml, add dependencies from Maven Central, run any goal from a run configuration and read the sources of the libraries you call — without installing Maven or a JDK.

  • Apache Maven 3.9
  • Maven Central with sources
  • JUnit 5 included
<dependencies>
    <dependency>
        <groupId>com.google.code.gson</groupId>
        <artifactId>gson</artifactId>
        <version>2.11.0</version>
    </dependency>
</dependencies>

Save pom.xml and press Run: Gson and its sources are downloaded on the next build.

Built on the tools Java and Kotlin developers already trust

Java 8 Java 11 Java 17 Java 21 Java 25 Kotlin 2 Maven Gradle Gradle Kotlin DSL Maven Central JUnit 5 Eclipse JDT google-java-format Step debugger
Apache Maven

What you get

Create, build and run Maven projects online. Edit pom.xml, pull dependencies from Maven Central with sources, run mvn goals and JUnit 5 tests on JDK 8–27.

  • Apache Maven 3.9

    Projects build with Apache Maven 3.9 on the JDK of the project, with the standard src/main/java and src/test/java layout.

  • Maven Central with sources

    Dependencies are downloaded on the next build together with their sources, so Go to Declaration opens real library code.

  • Goals as run configurations

    Maven configurations run any goals with profiles, -D properties, skip tests and offline mode.

  • Reload project

    After editing pom.xml, Reload Maven Project resolves dependencies and refreshes External Libraries.

  • Fast re-runs

    While pom.xml is unchanged, Run compiles only your sources with javac and skips Maven entirely.

  • Package and run a JAR

    Build the project to create a JAR and start it with a JAR Application configuration, the same way as java -jar.

How it works

Under the hood

  1. 01

    What happens when you build

    Maven runs in an isolated sandbox with your own local repository, so downloaded artifacts are reused by every later build of your projects. Compiler errors are parsed from the Maven output and shown in the editor and the Problems tool window.

    Network access during the build goes through a filtered proxy that only serves package repositories. Your program itself never gets internet access.

  2. 02

    Limits worth knowing

    Goals that start servers or deploy applications, such as spring-boot:run or jetty:run, are refused because programs cannot open network ports. Compiling, testing, packaging and running console programs all work.

FAQ

Questions, answered

Do I need Maven or a JDK installed?

No. Maven, every JDK from 8 to 27 and your local repository live on the server. A browser is enough.

Which Maven version is used?

Apache Maven 3.9, with the JDK selected for the project.

Can I run mvn test?

Yes. Run tests from the gutter, with Run All Tests, or create a Maven configuration with the test goal.

Can I open an existing Maven project?

Yes. Upload the project files or an archive with pom.xml and build it; dependencies are resolved on the first build.