-
Notifications
You must be signed in to change notification settings - Fork 3k
Sync naming convention for file dependency JARs #48800
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Sync naming convention for file dependency JARs #48800
Conversation
Thanks @reaver585! We do want to have a test for it though. We could adapt the reproducer provided by the user or come up with one on our own. Would you like to look into that? |
@aloubyansky yeah, sure, I can do this - it will anyways be useful for me to look at how testing is generally done. |
This comment has been minimized.
This comment has been minimized.
FYI, I will prepare the next 3.24.x tomorrow evening Paris time and it would be great if we could merge this by then. Thanks! |
cfd3aef
to
638bc59
Compare
@aloubyansky I have added the test that reproduces the issue. I'm sure it can be done in a cleaner fashion, but first, I wasn't sure it was needed since for now this is the only such test, and second, I'm not sure I could do that quickly - if we want to merge this before tomorrow's release. cc @gsmet |
Oh yeah, there also seems to be an issue in current main
This happens for me locally too. Looks like markdown tries to pull in dependencies that are not available in maven central. Don't know what's the deal with that, saw other CI runs in the repo failing because of this. |
Stumbled across this issue because I was having problems with my build of It seems like the path forward is to upgrade vaadin in the dev ui bom to 3.28.3 (which is how i was able to start building |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks a lot @reaver585 !
Thx for the info @ryandens. |
This makes Gradle's 'quarkusDependenciesBuild' task use same naming convention when producing jars for directory dependencies as JarResultBuildStep. Closes quarkusio#48768
638bc59
to
32c1d55
Compare
I just rebased this branch |
Thanks! |
This comment has been minimized.
This comment has been minimized.
Status for workflow
|
Status | Name | Step | Failures | Logs | Raw logs | Build scan |
---|---|---|---|---|---|---|
✖ | JVM Tests - JDK 17 | Build |
Failures | Logs | Raw logs | 🔍 |
✖ | JVM Tests - JDK 21 | Build |
Failures | Logs | Raw logs | 🔍 |
✖ | JVM Tests - JDK 17 Windows | Build |
Failures | Logs | Raw logs | 🔍 |
Full information is available in the Build summary check run.
You can consult the Develocity build scans.
Failures
⚙️ JVM Tests - JDK 17 #
- Failing: core/deployment
! Skipped: devtools/cli devtools/gradle/gradle-application-plugin devtools/gradle/gradle-extension-plugin and 379 more
📦 core/deployment
✖ io.quarkus.deployment.runnerjar.RetryResolutionOnMissingTmpFileErrorsTest.test
line 233
- History - More details - Source on GitHub
java.lang.AssertionError:
Expecting AtomicBoolean(false) to have value:
true
but did not.
at io.quarkus.deployment.runnerjar.RetryResolutionOnMissingTmpFileErrorsTest.assertAppModel(RetryResolutionOnMissingTmpFileErrorsTest.java:233)
at io.quarkus.deployment.runnerjar.PackageAppTestBase.initAugmentAction(PackageAppTestBase.java:146)
at io.quarkus.deployment.runnerjar.PackageAppTestBase.testBootstrap(PackageAppTestBase.java:156)
⚙️ JVM Tests - JDK 21 #
- Failing: core/deployment
! Skipped: devtools/cli devtools/gradle/gradle-application-plugin devtools/gradle/gradle-extension-plugin and 379 more
📦 core/deployment
✖ io.quarkus.deployment.runnerjar.RetryResolutionOnMissingTmpFileErrorsTest.test
line 233
- History - More details - Source on GitHub
java.lang.AssertionError:
Expecting AtomicBoolean(false) to have value:
true
but did not.
at io.quarkus.deployment.runnerjar.RetryResolutionOnMissingTmpFileErrorsTest.assertAppModel(RetryResolutionOnMissingTmpFileErrorsTest.java:233)
at io.quarkus.deployment.runnerjar.PackageAppTestBase.initAugmentAction(PackageAppTestBase.java:146)
at io.quarkus.deployment.runnerjar.PackageAppTestBase.testBootstrap(PackageAppTestBase.java:156)
⚙️ JVM Tests - JDK 17 Windows #
- Failing: core/deployment
! Skipped: devtools/cli devtools/gradle/gradle-application-plugin devtools/gradle/gradle-extension-plugin and 379 more
📦 core/deployment
✖ io.quarkus.deployment.runnerjar.RetryResolutionOnMissingTmpFileErrorsTest.test
line 233
- History - More details - Source on GitHub
java.lang.AssertionError:
Expecting AtomicBoolean(false) to have value:
true
but did not.
at io.quarkus.deployment.runnerjar.RetryResolutionOnMissingTmpFileErrorsTest.assertAppModel(RetryResolutionOnMissingTmpFileErrorsTest.java:233)
at io.quarkus.deployment.runnerjar.PackageAppTestBase.initAugmentAction(PackageAppTestBase.java:146)
at io.quarkus.deployment.runnerjar.PackageAppTestBase.testBootstrap(PackageAppTestBase.java:156)
@gsmet I'll look into RetryResolutionOnMissingTmpFileErrorsTest. |
This makes Gradle's 'quarkusDependenciesBuild' task use same naming convention when producing jars for directory dependencies as JarResultBuildStep.