jeddict-modeler

Jakarta EE 10 & MicroProfile application generator and modeler

Could not verifysource: GitHubhomepageJavaApache-2.0commit 496fb1893c0b

Java, Apache-2.0 licensed. The project labels itself: ddl, diagram, eclipselink, hibernate, jakarta ee, jakartaee, javaee and javaee8.

Argusic could not get jeddict-modeler running. An Argusic agent installed it in 13.2 minutes and hit 5 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

All 14 modules of the main Jeddict repo build successfully after importing JavaParser path fix. Tests could not execute because they require a full NetBeans IDE runtime.

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 50 of 100 (the mean of this project's run scores).

At a glance

verdict
Could not verify
Argusic Score
50 / 100
cost of the verifying run
$0.32 (measured)
recorded runs
2
last tested
stars
403
forks
45
open issues
68
watchers
34
size
56 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 jeddict-modeler, 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.

  • Tests fail: require NetBeans IDE 11.3+ platform runtime. Module system hangs on missing platform deps (commons-codec, commons-logging, gson, etc.)5 minutes
  • No JDK or Maven available in container4.1 minutes
  • Build failed: jpa-spec compilation - TypeSolver/SymbolReference imports use old javaparser package2.1 minutes
  • HTTP repo bits.netbeans.org unreachable (connection refused on port 80)1.5 minutes
  • Build failed: nbm plugin could not write to root-owned /work/jeddict-cluster0.5 minutes
Install time
13 minutes
Cold machine to finish
51 minutes
Errors hit and fixed
5 hit, 5 fixed with no human help
How the result was proved
mvn -f /work/repo -o -q install -DskipTests -Dnbm.build.dir=$HOME/jeddict-cluster exited 0; all 14 modules built successfully (jeddict-lib, jpa-spec, jcode-core, jcode-util, jpa-modeler, orm-generator, reverse-engineering, db-modeler, collaboration, relation-mapper, jsonb-modeler, installer, tests, examples, incubation)
Model tokens used
1,137,446
Exact commit tested
496fb1893c0b
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
Whether it works at all
this run verified nothing, so this page makes no claim either way

The end of the recording

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

    {"msg": "HTTP repo bits.netbeans.org unreachable (connection refused on port 80)", "fix": "Crea…
    {"msg": "Build failed: nbm plugin could not write to root-owned /work/jeddict-cluster", "fix": …
    {"msg": "Build failed: jpa-spec compilation - TypeSolver/SymbolReference imports use old javapa…
    {"msg": "Tests fail: require NetBeans IDE 11.3+ platform runtime. Module system hangs on missin…
  ],
  "test_depth": "tier3_none",
  "notes": "Jeddict is a NetBeans plugin project. The main maven build succeeds after fixing javapa…
  "verified_how": "mvn -f /work/repo -o -q install -DskipTests -Dnbm.build.dir=$HOME/jeddict-cluste…
  "final_state": "All 14 modules of the main Jeddict repo build successfully after importing JavaPa…
}
tokens used
1,137,446

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

  • Installed in 13.2 minutes.
  • Recovered from all 5 errors without a human stepping in, which says the failures are documented well enough to solve.
  • Licensed Apache-2.0, as reported by its host.
  • Measured 2 times, so the result is not a one-off.

What did not, or is not known

  • An agent with no time limit did not get it running.

Also tested, in the same area

Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.

Run history

tested byattemptoutcomescorecost USDwhen
Argusic Runner2/3Did not run50.000.32
Argusic Runner1/3Did not run50.000.26

Topics (from GitHub)

ddldiagrameclipselinkhibernatejakarta-eejakartaeejavaeejavaee8jax-rsjpajsonbmicroprofilemicroservicesmodelernetbeansormpayarapayara-micropayara-serversql

Embed the badge

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

[![Tested by Argusic](https://argusic.com/badge/jeddict-modeler.svg)](https://argusic.com/subject/jeddict-modeler)

Questions

Does jeddict-modeler run?
Argusic could not verify that jeddict-modeler runs. Argusic installed and launched it on a clean machine in 13 minutes, hitting 5 errors on the way, and recorded the session.
How did Argusic test jeddict-modeler?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 496fb1893c0b. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test jeddict-modeler?
The run that produced this verdict cost $0.32: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does jeddict-modeler take to install?
13.2 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 jeddict-modeler need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing jeddict-modeler?
5 things broke in the recorded run, and 5 were fixed without human help. Each one, and the time it cost, is listed on this page.
Where is the evidence for jeddict-modeler?
All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.

Discussion