Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Processor yield NPE under some circonstancies

Open
#320 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
java
Domain
compilers

Research direction

Start with the CodeGenProcessor and the linked IDEA-258659 reproducer. Rebuild the sample project with IntelliJ 2020.2.4 and 2020.3 using JDK 8 to confirm when the NPE occurs, then compare the processor behavior with the IntelliJ reports. Done means the processor no longer fails with an NPE under the reported build configuration.

Written by the indexing model from the issue text.

Description

bug
Questions

When using IntelliJ > 2020.2.4 the build fails with NPE in the CodeGenProcessor.
This sound very much like an intelliJ issue however their investigation seem to aim for a lack of robustness in some processor implementations.
Here is the ticket I filled in at IntelliJ' support : https://youtrack.jetbrains.com/issue/IDEA-258659
This other ticket may be of interest too: https://youtrack.jetbrains.com/issue/IDEA-257871

Version 3.5.3
Context

Problem ocurred while uprading from IntelliJ 2020.2.4 to 2020.3

Do you have a reproducer?

The following sample project builds againts intelliJ 2020.2.4 and not against 2020.3

Steps to reproduce
  1. clone repo
  2. build -> rebuild project
Extra
  • windows 10 pro
  • oracle jdk8u201
  • For those who are looking for a workround, in the link I provided above, they explained how to configure the -Djps.track.ap.dependencies=false flag, this worked for me.
Dominant language
Java
Stars
111
Forks
88
PR merge metrics
No merged PRs in 30d

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from eclipse-vertx/vertx-codegen

All issues in eclipse-vertx/vertx-codegen

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.