You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since version 26.3.x, GitHub releases only provide source tarballs (arcadedb-*-sources.jar) – no prebuilt JDK-21 binary distributions. The CI packaging pipeline fails during the package phase due to JDK incubator module visibility issues with jdk.incubator.vector in the Javadoc generation step (see #3532).
Impact: Users must build from source with mvnw.cmd clean package -DskipTests, which requires Maven, JDK 21, and ~30 minutes build time. This is a significant barrier to adoption and upgrades, especially on Windows where the build toolchain setup is non-trivial.
Suggested fix:
Add a CI step that produces the binary distribution (arcadedb-*.zip) even if Javadoc generation fails (e.g. by disabling Javadoc in the release profile), OR
Fix the Javadoc plugin configuration to handle the jdk.incubator.vector module properly (see Deploy workflow in error #3532)
Since version 26.3.x, GitHub releases only provide source tarballs (
arcadedb-*-sources.jar) – no prebuilt JDK-21 binary distributions. The CI packaging pipeline fails during thepackagephase due to JDK incubator module visibility issues withjdk.incubator.vectorin the Javadoc generation step (see #3532).Impact: Users must build from source with
mvnw.cmd clean package -DskipTests, which requires Maven, JDK 21, and ~30 minutes build time. This is a significant barrier to adoption and upgrades, especially on Windows where the build toolchain setup is non-trivial.Suggested fix:
arcadedb-*.zip) even if Javadoc generation fails (e.g. by disabling Javadoc in the release profile), ORjdk.incubator.vectormodule properly (see Deploy workflow in error #3532)Current workaround:
This produces the binary distribution but requires a full local Maven build.
Environment: