Regression in 8.2: StackOverflowError w/ Gradle 8.2 + Quarkus 2.16.7 (latest) #25579
Assignees
Labels
a:bug
has:reproducer
Indicates the issue has a confirmed reproducer
in:dependency-resolution
engine metadata
Milestone
Comments
1 task
|
Thank you for providing a valid reproducer. The issue is in the backlog of the relevant team, but this area of Gradle is currently not a focus one, so it might take a while before a fix is made. |
|
Update: Gradle 8.2 works with the Quarkus 3 Gradle plugin, but not w/ the Quarkus 2 Gradle plugin. |
jbartok
added
the
closed:not-fixed
|
Thank you for your interest in Gradle! This issue needs a decision from the team responsible for that area. They have been informed. Response time may vary. |
jbartok
added
👋 team-triage
|
This will be fixed in 8.2.1 by #25626 |
bot-gradle
added a commit
that referenced
this issue
Jul 6, 2023
…solve current project Prior to 8.2, addAllLater hooks on a configuration could resolve other configurations in the same project in order to determine the dependencies to add. 8.2 added a change which eager calculated confguration metadata dependenices for all consumable variants in the same project, causing a stackoverflow. This once again makes configuration dependency calculation lazy, avoiding a stackoverflow. Note, a stackoverflow will likely still happen if the configuration with the lazy dependencies selects itself. But, this makes no sense conceptually. Fixes: #25579 Co-authored-by: Justin Van Dort <jvandort@gradle.com>
ljacomet
removed
to-triage
👋 team-triage
|
Hey @snazy, Could you confirm that the 8.2.1 nightly fixes this reported issue? |
|
Looks good! |
snazy
added a commit
to snazy/nessie
that referenced
this issue
Jul 14, 2023
Gradle 8.2.0+8.2.1 have serious bugs in combination with Quarkus, causing builds to fail with either a [`StackOverflowException`](gradle/gradle#25579)) or [`ConcurrentModificationException`](gradle/gradle#25751). This change reverts Gradle back to 8.1.1 and also cleans up the failed, nowhere (yet) published Nessie releases 0.65.0+0.65.1.
snazy
added a commit
to snazy/nessie
that referenced
this issue
Jul 14, 2023
Gradle 8.2.0+8.2.1 have serious bugs in combination with Quarkus, causing builds to fail with either a [`StackOverflowException`](gradle/gradle#25579)) or [`ConcurrentModificationException`](gradle/gradle#25751). This change reverts Gradle back to 8.1.1 and also cleans up the failed, nowhere (yet) published Nessie releases 0.65.0+0.65.1.
snazy
added a commit
to projectnessie/nessie
that referenced
this issue
Jul 14, 2023
Gradle 8.2.0+8.2.1 have serious bugs in combination with Quarkus, causing builds to fail with either a [`StackOverflowException`](gradle/gradle#25579)) or [`ConcurrentModificationException`](gradle/gradle#25751). This change reverts Gradle back to 8.1.1 and also cleans up the failed, nowhere (yet) published Nessie releases 0.65.0+0.65.1.
This was referenced Jul 31, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Expected Behavior
No
StackOverflowErrorCurrent Behavior
java.lang.StackOverflowErrorw/ repeated stack frames:Context (optional)
This failure happens since Gradle 8.2. Gradle 8.1.1 works fine (regression with Gradle 8.2).
This happens with Quarkus 2.16.7.Final (Quarkus Gradle plugin version).
The failure seems not to happen with Quarkus 3.1.3.Final (the Quarkus Gradle plugin has been heavily changed in Quarkus 3). Haven't sorted out the task-dependency issues yet, so haven't seen the build passing w/ Quarkus 3 + Gradle 8.2 yet.
Tried with Java 20.0.1 + 17.0.7.
Steps to Reproduce
git clone https://github.com/projectnessie/nessie.gitcd nessie./gradlew compileJavaGradle version
8.2
Build scan URL (optional)
CI w/ Quarkus leads to build scan
CI w/o Quarkus leads to build scan
Your Environment (optional)
Linux 6.4.0
No additional/changed Gradle settings than in the source repo's
gradle.propertiesThe text was updated successfully, but these errors were encountered: