Open gayanper opened 4 months ago
If we can agree on a good strategy to handle this I can help on the implementation with a PR.
Your analysis sounds good and it would be great if you can help here. There are 2 issues you may want to look at: #222 and #215 , I think you'll need to tackle them in this order.
Note that the current code tends to be a too low-level: setting the Options and Paths for instance would probably better be done as part of the JavacTask creation (which allows to pass those settings). So if you agree a refactoring here would help, feel free to proceed with it.
When loading the CU in gradle project with a annotation processor like Lombok, there are multiple output folders emitted which cause a validation error in JavaFileManager in used.
Gradle file
The issue lies at the following line
https://github.com/eclipse-jdtls/eclipse-jdt-core-incubator/blob/fix-multi-source-output-dirs/org.eclipse.jdt.core.javac/src/org/eclipse/jdt/internal/javac/JavacUtils.java#L96
I'm not really sure if the default path is used or not since I assume that is something the build ship plugin provides as part of the eclipse project configuration.
These are the received values
I wonder if buildship will do anything specific in this scenario when running on Javac mode. So one option is to resolve the conflict by choosing the best path. In this case just ignore the source path which is part of the bin provided that we know
bin
in the build out in this place.@mickaelistria WDYT ?