1JPM

1 Java Project Manager (1JPM), is a Maven/Gradle alternative with a twist. It's a single Java file itself, which should be edited by you to configure your project. Meaning instead of writing XML or Groovy/DSL, your build file is Java code too.

To build your project, simply drag-and-drop the JPM.java file into your project, open a terminal and execute java JPM.java (Java 11 and above).

Good to know:

• This repository functions as a template too
• 1JPM is Maven based, thus great IDE support by default
• 1JPM includes some extra plugins to increase runtime safety and provide additional features out of the box

public class JPM {
    public static class ThisProject extends JPM.Project {
        public ThisProject() throws IOException, InterruptedException {
            this(null);
        }
        public ThisProject(List<String> args) throws IOException, InterruptedException {
            // Override default configurations
            this.groupId = "com.mycompany.myproject";
            this.artifactId = "my-project";
            this.version = "1.0.0";
            this.mainClass = "com.mycompany.myproject.MyMainClass";
            this.jarName = "my-project.jar";
            this.fatJarName = "my-project-with-dependencies.jar";

            // If there are duplicate dependencies with different versions force a specific version like so:
            //forceImplementation("org.apache.commons:commons-lang3:3.12.0");

            // Add dependencies
            implementation("org.apache.commons:commons-lang3:3.12.0");
            testImplementation("org.junit.jupiter:junit-jupiter-api:5.10.3");

            // Add compiler arguments
            addCompilerArg("-Xlint:unchecked");
            addCompilerArg("-Xlint:deprecation");

            // Add additional plugins
            //putPlugin("org.codehaus.mojo:exec-maven-plugin:1.6.0", d -> {
            //    d.putConfiguration("mainClass", this.mainClass);
            //});

            // Execute build
            if(args != null){
                generatePom();
                if(!args.contains("skipMaven"))
                    JPM.executeMaven("clean", "package");//, "-DskipTests"); 
                // or JPM.executeMaven(args); if you prefer the CLI, like "java JPM.java clean package"
            }
        }
    }

    public static class ThirdPartyPlugins extends JPM.Plugins{
        // Add third party plugins below, find them here: https://github.com/topics/1jpm-plugin?o=desc&s=updated
        // (If you want to develop a plugin take a look at "JPM.AssemblyPlugin" class further below to get started)
    }

    // 1JPM version 3.0.3 by Osiris-Team: https://github.com/Osiris-Team/1JPM
    // To upgrade JPM, replace everything below with its newer version
}

Above you can see the example configuration which runs the clean package tasks. This compiles and creates a jar file from your code, and additionally creates the sources, javadoc and with-dependencies jars.

Additional goodies and FAQ

1JPM automatically resolves parent and child projects

1JPM helps porting your multi-module project

1JPM can create native executables

1JPM can create native installers

1JPM is Maven based

1JPM has plugins

1JPM saves you time

How can I modify the generated pom.xml file? How to use the XML class?

1JPM is able to auto-update itself

Why a single file?

Pros

• IDEs should provide decent auto-complete when JPM.java is in the project root (where your pom.xml/build.gradle) usually is.
• To access all your IDEs fancy features, you can also add JPM.java to ./src/main/java. This also grants the rest of your project easy access to its data, like your projects version for example. Just make sure that your working dir is still at ./ when executing tasks.
• Simple drag and drop installation.
• Direct access to the source of 1JPM and what happens under the hood for those who like exploring or better understanding how something works, which can be helpful if issues arise.

Cons / Todo

• Developing plugins is tricky (if you want them to be more complex) since you can't really use third-party dependencies at the moment. A workaround for this would be developing a task like "minifyProject" which would merge a complete project into 1 line of code,

Tipps

• You can use ChatGTP (or another LLM) to easily port your current Maven/Gradle based project over to 1JPM, by sending it the above example ThisProject class and your current build details files (pom.xml/build.gradle), then prompting it something like: "Port my current Maven/Gradle project to the JPM build tool, by modifing the ThisProject class accordingly". If you have additional plugins also send it an example plugin from within the JPM class.

Funding

I am actively maintaining this repository, publishing new releases and working on its codebase for free, so if this project benefits you and/or your company consider donating a monthly amount you seem fit. Thank you!