-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
[CI] - Quarkus Super Heroes + Quarkus main #23612
[CI] - Quarkus Super Heroes + Quarkus main #23612
Comments
The build is still failing:
|
The build is still failing:
|
The build is still failing:
|
Build fixed:
|
Unfortunately, the build failed:
|
The build is still failing:
|
@geoand is this a regression on Quarkus main? Error: ] Some problems were encountered while processing the POMs:
Error: 'dependencies.dependency.version' for io.quarkus:quarkus-junit5-vertx:jar is missing. @ line 109, column 17
@
Error: The build could not read 1 project -> [Help 1]
Error:
Error: The project io.quarkus.workshop.super-heroes:rest-heroes:1.0 (/home/runner/work/quarkus-super-heroes/quarkus-super-heroes/current-repo/rest-heroes/pom.xml) has 1 error
Error: 'dependencies.dependency.version' for io.quarkus:quarkus-junit5-vertx:jar is missing. @ line 109, column 17 |
It's the result of #23905. From the description:
|
Got it. Thanks you. So does that mean until 2.7.3 is out this CI will fail every day? |
Why do you say that? CI should be green once you make the changes mentioned above. |
Is |
Nope. Isn't CI testing against Quarkus |
It is. Which goes to my earlier comment that I can't make any changes until 2.7.3 is released, which also means the daily CI will continue to fail each day because of it. There isn't anything I can do to fix it until 2.7.3 is out. |
|
Sounds good. Thanks for the help! Since this is a breaking change in a minor release I'd make sure it's well documented in the release notes :) |
Yup, will do |
The build is still failing:
|
The build is still failing:
|
I just merged in changes for |
Build fixed:
|
I think I understand what is happening here. #43005 took away the renames, so now See this:
So what I think we will need to Quarkus LangChain4j depend on Quarkus 3.15 when that comes out as we would then be able to use the new artifact names. |
Why can't we change the openai dependency on If we wait for 3.15 to come out, then anyone using quarkus-langchain with Quarkus 3.15 will be broken until a new quarkus-langchain is released. |
We can, we just need to depend on |
That's not true - with the current situation, |
Ah yes you're right. |
That is correct |
So then I think we have 2 options until 3.15 is out and Quarkus LangChain4j is updated:
Personally I like option 2 (my OCD doesn't like things that continually fail :) ) |
I strongly agree with option 2 |
What is the branch name for 3.15? I don't see one. |
Thanks for the analysis, @edeandrea. The same root cause also caused failures in the groovy and pact ecosystem CIs.
|
You're welcome @holly-cummins. Unfortunately for the super heroes the problem is in a transitive dependency, so I'm not sure there's a way to re-write the dependency graph? I'm no Maven expert. I know it could easily be done in Gradle :) |
It will be a continuation of |
Hey @bdemers do you know if there is a way in Maven to add a dependency rewrite rule on the fly during the build? Meaning if one of my project's transitive dependencies depends on A, maybe I want to re-write that dependency to B? Like you can do with Gradle (https://docs.gradle.org/current/userguide/resolution_rules.html#sub:conditional_dependency_substitution). In Gradle I could do something like this in my configurations.all {
resolutionStrategy {
eachDependency { dependency ->
if ((dependency.requested.group == 'io.quarkus') && (dependency.requested.name == 'quarkus-rest-client-reactive-jackson')) {
dependency.useTarget group: 'io.quarkus', name: 'quarkus-rest-client-jackson', version: dependency.requested.version
}
}
}
} |
So for now point it at the |
Yup |
See quarkusio/quarkus-super-heroes@d21e8db Now let's not forget to revert once 3.15 is out :) |
👌🏽 |
Not really, but you could create a Maven extension could probably do it, but IMHO, that might obscure what is going on. If you just want to test the same project with one lib (reactive), and run the build again to test it out with another (non-reactive) you could create profiles, and run the build twice: If you want to run a build and test the integration of both libraries in the same build you could do that too, but how it's structured may depend on how your project is laid out (and it's goals, e.g. if the goal is testing or explaining to others how they should test a typical app).
If that doesn't help (or I'm way off on what you are trying to do) let me know and we can chat for a few minutes, and I see if I can point you in the right direction! |
Thanks for chiming in @bdemers! The issue here is that in Quarkus itself, version 3.9+ renamed So now the build of the application fails. We were trying to figure out a clever way for the application to enforce the placeholders, which can be easily done in Gradle :) |
Ahh! Changing a GAV is hard! Depending on what you did for the placeholder redirects, (Maven empty maven modules, or actual maven repository relocation files) My suggestion would be to keep an empty module using the old name, that depends on the new name, add a deprecated note in the pom (nobody will read it though). We had a similar story with JJWT. 🤔 Another idea would be to deploy an empty jar with an odd version name like |
Thanks a lot for the insight @bdemers. Just for completeness I'll add that we did have relocations for the artifact in question, but those were removed since we don't want to maintain them forever. |
The build is still failing:
|
The build is still failing:
|
The build is still failing:
|
The build is still failing:
|
This issue will be open and closed dependent on the state of https://github.com/quarkusio/quarkus-super-heroes building against Quarkus main snapshot.
If you have interest in being notified of this subscribe to the issue.
Closing #23425 in favor of this one.
The text was updated successfully, but these errors were encountered: