redhat-developer / redhat-developer/vscode-java
Annotation processor in project incorrectly yields "[Java] <generated type> cannot be resolved to a type"
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 2.3k
- Forks
- 546
- Avg merge
- 20h 1m
- Merged PRs (30d)
- 11
Description
I have access to a specific (large) project here which makes use of
@SupportedAnnotationTypes({"the.namespace.TheAnnotation"})
@SupportedSourceVersion(SourceVersion.RELEASE_10)
to create an annotation processor
public class TheAnnotationProcessor extends AbstractProcessor {
for an annotation the.namespace.TheAnnotation in that project
public @interface TheAnnotation {
which produces an interface (e.g. GeneratedInterfaceSpecificMapper, see below) with plenty of default. In the very same project, this annotation is also applied to some classes,
@TheAnnotation(Specific.class)
public class SpecificMapper implements GeneratedInterfaceSpecificMapper {
Evidently, maven discovers the annotation, the annotation processor, runs code generation through the processor (files appear in generated-sources/annotations/...) and is able to also compile the source files that make use of the GeneratedInterfaceSpecificMapper.
The vscode plugin flags the type GeneratedInterfaceSpecificMapper as faulty, with "[Java] cannot be resolved to a type". This seems to indicate that the vscode plugin is not aware of the generated artefacts in generated-sources/annotations/...
I have had a look at https://www.baeldung.com/java-annotation-processing-builder to see whether this produces the error - alas, that setup there seems to be too clean / too simplistic to trigger the problem.
Environment
- Operating System: Linux Fedora 28
- JDK version: 10.0.2
- Visual Studio Code version: 1.28.2
- Java extension version: java-0.33.0-1252.vsix
Steps To Reproduce
<large project, will try to find time to reduce>
Current Result
- builds fine in maven
- red squiggles in IDE / syntax check failure
Expected Result
- builds fine in maven
- no red squiggles in IDE
Additional Informations
Not sure whether this related to the issues reported for Lombok - e.g #580 or #458
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Begin with the Java extension's annotation-processing path and the generated-sources/annotations/... output described in the report; reproduce the Maven-versus-IDE discrepancy using the referenced annotation processor and GeneratedInterfaceSpecificMapper. A reduced project or equivalent reproduction is needed, and done means Maven still builds while the IDE no longer reports the generated type as unresolved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, typescript, vscode
- Domain
- developer-experience, devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100