Replies: 3 comments 1 reply
-
|
Java extension doesn't support delegating to 3rd party build tools for compilation yet, but this would be a direction we'd like to go forward in future. Back to your case, the solution we need to figure out is how to make JDT compiler to support the MapStruct annotation better? |
Beta Was this translation helpful? Give feedback.
-
|
Looks like the root cause is that JDT does not recognize the SPI config: https://github.com/dawosch/vscode-java-extension-compiler-error/blob/main/mapstruct-accessing-strategy/src/main/resources/META-INF/services/org.mapstruct.ap.spi.AccessorNamingStrategy. Not sure if there is a workaround for this issue now. |
Beta Was this translation helpful? Give feedback.
-
|
@jdneo @testforstephen See redhat-developer/vscode-java#3007 (comment) |
Beta Was this translation helpful? Give feedback.
-
|
|
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hey, i want to know if this extension is using a specific java compiler?
When i build my java project with maven and my local installed java version in the source files of my classes is the compiler javac.
But when i start my project with the spring boot dashboard extension, the debugger extension always compiles my project and then the compiler changed to Eclipse JDT (IDE).
Maven compile step:
Java Debugger compile step:
It seems that the eclipse compiler ignores my classpath, because the generated files are different.
With the javac compiler everything works, with the eclipse compiler values will not be settet.
The error occures only with the "MapStruct" dependency and a custom naming strategy.
MapStruct installation
Custom naming strategy
But maybe i'm on a wrong way. But this is the only different i noticed.
Edit:
Here i created a repo with all the files to reproduce the error: Repository
Step 1: Clone the repo
Step 2: run the command "mvn -U clean install" on the root folder
Step 3: Look at the file "TestMappterInterfaceImpl" in "app/target/generated-sources/annotations/con/example/demo"
You will notice that on line 20 the setter is generated
Step 4: Run the "app" project from the "Spring Boot Dashboard" extension
Step 5: Look at the same file
You will see that the compiler has changed and the setter isn't there
Beta Was this translation helpful? Give feedback.
All reactions