How to prevent quarkus overwrite packages after compilation? #50008
Unanswered
MikaelAnderssonWigander
asked this question in
Q&A
Replies: 2 comments
-
In my original repo it creates this error bit not in this small reproducer…
|
Beta Was this translation helpful? Give feedback.
0 replies
-
I can circumvent this by telling the mapper to use "jakarta-cdi" instead. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
This is a weird behavior and I don't know if the subject is correct but that is what's happening.
I have a Quarkus application where I use MapStruct to map between objects.
MapStruct is using the annotation processor and generates Impl classes at compile time.
Running on the latest versions of Quarkus and MapStruct and on Java 21 I want to use the jakarta package.
My Mapper class is defined like this:
When doing
mvn compile
it will create this Impl class:When then running it using the quarkus:dev or thru vscode Quarkus extension, it will compile again but now the
@Inject
is now dependent on the javax package.What the?
Something is wrong here and I don't know what to do to fix this.
Here's a small reproducer:
https://github.com/MikaelAnderssonWigander/code-with-quarkus
Beta Was this translation helpful? Give feedback.
All reactions