1JPM

Maven/Gradle alternative with a twist: its a single Java file! Edit it to configure your project.

Runssource: GitHubJavaMITcommit b828b6579084

Java, MIT licensed. The project labels itself: build tool, dependecy manager and project management.

1JPM runs. An Argusic agent installed it in 11 minutes and hit 4 errors on a clean machine with no GPU, and the whole session was recorded.

In /work/repo, `java JPM.java` (root JPM.java added) and `./mvnw` are installed and run cleanly: the JUnit test suite runs 1 test with 0 failures, Maven clean package builds the jars, and `java -jar target/my-project.jar` prints 'Hello World!'.

What the agent ended up with on a clean machine, in its own words. How this is measured

Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 95 of 100 (the mean of this project's run scores).

At a glance

verdict
Runs
Argusic Score
95 / 100
cost of the verifying run
$0.06 (measured)
recorded runs
1
last tested
stars
227
forks
5
open issues
2
watchers
1
size
0 MB
created
last push

Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.

What was measured

From the run that decided this verdict. Every line is a recorded value, not an estimate.

Time lost to each failure while testing 1JPM, drawn from the recorded run
Every bar is a failure the agent recorded, with the time it cost. Drawn from this run, not from anywhere else.

What went wrong, in the agent's own words

The agent's own words, worst first, never rewritten into advice.

  • As-shipped, the README headline command `java JPM.java` fails from repo root with 'Could not find or load main class JPM.java' because the 'drag-and-drop' JPM.java file is only shipped under src/main/java/com/mycompany/myproject/ in this template repo; the pre-existing IDE tasks instead invoke `java ./src/main/java/com/mycompany/myproject/JPM.java`.4 minutes
  • No JDK or Maven installed in the container (no root to apt-get): `java`/`javac`/`mvn` not found.2 minutes
  • Ran `git checkout pom.xml` expecting to restore the committed pom and verify the tool's own regeneration; observed it rewrote the whole tree (removed JPM.java, .mvn/, mvnw), so I restored the committed pom and the fixed files.1 minute
  • repeated run of `java JPM.java` from repo root1 minute
Install time
11 minutes
Cold machine to finish
5 minutes
Errors hit and fixed
4 hit, 3 fixed with no human help
How the result was proved
./mvnw -B clean test exited 0 with 'Tests run: 1, Failures: 0, Errors: 0, Skipped: 0' and BUILD SUCCESS; java -jar target/my-project.jar printed 'Hello World!'; java JPM.java from repo root exited 0, printed 'Generated pom.xml file.', ran 'clean package' with Tests run: 1, Failures: 0 and BUILD SUCCESS
Model tokens used
268,744
Exact commit tested
b828b6579084
Container image
sha256:cdd920bce783

What was not measured

The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.

Peak GPU memory
this ran on a CPU machine, so there was no GPU to sample
Behaviour over a long run
each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load

The end of the recording

The last lines of the terminal session that decided this verdict, exactly as they were recorded.

target/my-project.jar
 M pom.xml
?? JPM.java
All checks pass. Final state: `java JPM.java` works from repo root, tests run green, jar runs and p…
exec
/bin/sh -lc 'date -u +%H:%M:%S' in /work/repo
 succeeded in 0ms:
13:58:52
Everything is done and verified end-to-end; final report below.
tokens used
268,744
Everything is done and verified end-to-end; final report below.

Replay the whole session, every command from a clean machine to this point.

How it was tested

One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.

Strengths and limits

Measured facts, not opinions. How this is written.

What went well

  • Reached a running state on a clean machine, with the session recorded.
  • Installed in 11 minutes.
  • Ran without a GPU, so it does not need one to start.
  • Licensed MIT, as reported by its host.

What did not, or is not known

  • Hit 4 errors during setup, 1 of which were not solved.
  • Measured once so far. A single attempt shows it can run, not that it runs reliably.

What it is a reasonable choice for

  • Trying it on a laptop or a small server: it reached a running state without a GPU.

Run history

tested byattemptoutcomescorecost USDwhen
Argusic Runner1/3Runs95.000.06

Topics (from GitHub)

build-tooldependecy-managerproject-management

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/1JPM.svg)](https://argusic.com/subject/1jpm)

Questions

Does 1JPM run?
Yes. 1JPM runs. Argusic installed and launched it on a clean machine in 11 minutes, hitting 4 errors on the way, and recorded the session.
How did Argusic test 1JPM?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit b828b6579084. One attempt is recorded, and the full method is on the methodology page.
What did it cost to test 1JPM?
The run that produced this verdict cost $0.06: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does 1JPM take to install?
11 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
Does 1JPM need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing 1JPM?
4 things broke in the recorded run, and 3 were fixed without human help. Each one, and the time it cost, is listed on this page.
Where is the evidence for 1JPM?
The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.

Discussion