-
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
Quarkus 3.0 codestarts for Gradle have javax
in allopen
rather than jakarta
#30582
Comments
Looks like we need to apply the changes in the following commit too in 3.0: 9a74058#diff-1fdf13c3faf1e270925515b7c829a57d03c1e4742330f889b30b369976928005R303-R304 |
right, I will update kotlin codestart code. |
Actually it was already updated in 51e819c and should be available in the next release |
Ah, sorry for an invalid issue! |
Actually it doesn't seem to be fixed - https://github.com/quarkusio/quarkus/blob/3.0/independent-projects/tools/base-codestarts/src/main/resources/codestarts/quarkus/buildtool/gradle/kotlin/build.tpl.qute.gradle I think @glefloch 's PR may fix it |
I will have a look as if you’re using Alpha3, it should be already fine. |
There's something fishy. AFAICS, the Gradle Kotlin script is OK: But the Gradle one is not: I have no idea yet what's going on. I'm digging. |
I'm not sure yet. I think it fixes the issue with the gradle file AFAICS (but I'm unsure as I have no real idea about what was the initial issue...) but the kts file was already correct so I need to test it more. |
BTW, I'm still unsure as to why the Gradle Kotlin Script build file also has the issue while this particular file has been transformed. |
Describe the bug
Not sure if intentional, but generating a Quarkus 3.0 Gradle KTS codestart gives me:
Expected behavior
No response
Actual behavior
No response
How to Reproduce?
No response
Output of
uname -a
orver
No response
Output of
java -version
No response
GraalVM version (if different from Java)
No response
Quarkus version or git rev
No response
Build tool (ie. output of
mvnw --version
orgradlew --version
)No response
Additional information
No response
The text was updated successfully, but these errors were encountered: