The Server was using a SynchrnousQueue to coordinate the main thread
and the background thread that receives the request from the client.
A SynchronousQueue only allows insertions when a corresponding call
to `get` is in progress. However, since the receiver thread is started
before the call to `get`, there was a short time window, where the call
to `queue.offer` could fail and simply return `false`. This return code
was ignored.
A possible solution would have been to call `put` instead of `offer`,
but I decided to replace the queue with a Future, since we only wait
for a single element.
This was a small discrepancy to the output of vanilla Maven and made the output
hard to read, since the failure class name started right after the message without
any whitespace in between.
Fixing terminal on Windows.
changes:
* added missing jline-native to dist
* up GraalVM to 22
* introduce `--diag` on client
* up SVM version, cleanup of GraalVM params
Fixes#1032
Changes:
* `release-build.sh`: Just do not push. This allows one to locally verify the outcome, and push (for now manually like `git push origin mvnd-1.x --tags`). Added reminder message.
* `release.yaml`: whenever mvn would resolve deps, make sure release settings XML is present. It does not stir anything if Maven is in Central, but as in this moment, maven is still staged only.
* Pin docker images used for native compilation
* Update docker images
* Make mvnd-1.x buildable with Java 21 (#1018)
So far it was buildable ONLY with Java 17, but only due
single IT: it used old Quarkus version that refused to
work on Java 21.
Ported updates from mvnd master and now mvnd-1.x branch
can also be build without any problem with Java 21.
* Update RELEASING
* Adding two changed binaries as well
---------
Co-authored-by: Tamas Cservenak <tamas@cservenak.net>
So far it was buildable ONLY with Java 17, but only due
single IT: it used old Quarkus version that refused to
work on Java 21.
Ported updates from mvnd master and now mvnd-1.x branch
can also be build without any problem with Java 21.
And use JNI (and FFM) instead.
Changes:
* use DefaultClient from master (thanks @gnodet !)
* drop jansi (as DefaultClient should not depend on it)
* introduce two new jline3 terminal backends: jni and ffm (used on Java 22+)
* tested/verified (thanks @wendigo )
GH Action and related changes to finally cover all targeted OS/platforms with native binary.
Changes:
* no source change
* POM change: using released Maven 3.9.8 (and added access to staged Maven 3.9.8)
* Provide 4 plaf binaries: linux amd64, windows amd64, mac amd64 and mac aarch64
* adopt GH workflows for these changes (using "OS" alone is not enough)
* adopt generally GraalVM naming and use them consecutively
Changes:
* no source changes
* (build) expel all versions from child modules: they must be all top level depMgmt or pluginMgmt
* (build) Top POM contains GAVs while child modules GA+scope. This tremendously simplifies maintenance.
* (javadoc) fix Javadoc errors
Updates:
* use latest Maven 3.9.8-SNAPSHOT (TS locked version, controlled deploy by me)
* AssertJ 3.26.0
* Takari Smart Builder 0.6.6
* Sisu 0.9.0.M3
* maven wrapper 3.3.2 w/ scripts
This brings mvnd-1.x in "releasable" state (once Maven 3.9.8 is out).
(same as on master, align with master)
Changes:
* ~roaster 2.29.0.Final~ (bytecode is banned by enforcer, is newer than allowed)
* testcontainers 1.19.8
* picocli 4.7.6
* jline 3.26.1
* javassist 3.30.2-GA
The "happy path" should happen without anything thrown, unsure why here runtime ex is rethrown, others swallowed.
Change: just remove the try/catch and make method throw Exception (diff best seen with whitespace ignored).
Fixes#957Fixes#966
Most of cumulative things dependabot reported, plus more.
Changes:
* use plugins from parent (instead to double-maintain them here as well)
* general cleanup, add property where there are 2+ uses for it
* update plugins not present in parent
* non-key dependencies (maven3, maven4, graalvm not touched) updates
Port Maven 3.9.7 config and new properties (session.root/top)
into Daemon m39.
The IT got this property as it triggers exception (failure)
if mvn39 could not "discover" top directory.
Fixes#910
Changes:
* Cumulative update of GH flow
* Graal update
* Add concurrency
* Add -V to see what maven is used
* Use same Java version for def build
* Apply @gzm55 advice
Changes:
* parent POM 42
* unset release where needed (makes com.sun pkg unreachable)
* explicitly index as parent disables "implicit" AP
* remove redundtant stuff
* update dependabot to take care of workflow as well (as mvnd uses own)
