JPS incremental annotation processing is disabled. Compilation results on partial recompilation may be inaccurate

Question

Since IntelliJ IDEA 2020.3.2 (I use Community Edition), I started getting:

Parsing java... [applicationname]
java: JPS incremental annotation processing is disabled. Compilation results on partial recompilation may be inaccurate.
Use build process "jps.track.ap.dependencies" VM flag to enable/disable incremental annotation processing environment.
Writing classes

warning, upon running the application within the IntelliJ IDEA.

This actually happens during the build phase, when you run your application for the "first" time (to be more precise, when target (or whatever you have configured as a building result directory) is being built).

What does this message mean?

https://stackoverflow.com/a/73973709/6150881 – Rabhi salim Oct 06 '22 at 12:30 — Rabhi salim, Oct 06 '22 at 12:30

score 29 · Answer 1 · edited Aug 15 '22 at 18:15

29

As IDEA's build is incremental, it uses wrapper interfaces in order to collect some data that will help incremental analysis to correctly compile files affected by changes.

The -Djps.track.ap.dependencies=false option is added in: File > Settings/Preferences > Build, Execution, Deployment > Compiler. Then field Build process VM options disables collection of dependencies specified by an annotation processor when Filer methods are called.

In later versions of IntelliJ, the settings is now under: File > Settings > Build, Execution, Deployment > Compiler, then field Shared build process VM options

See some more details in this issue: IDEA-252069.

edited Aug 15 '22 at 18:15

banan3'14

3,810
3
24
47

answered Feb 12 '21 at 15:00

Andrey

15,144
25
91
187

11

Thank you for the answer; however, to me, this reads as a gibberish. Maybe you know the background context.. but not all do. Could you elaborate on what does it mean, that "IDEA's build is incremental"? what are "wrapper interfaces"? what for?.. what **some** data(this seems a new thing..) is IDEA collecting? – Giorgi Tsiklauri Feb 24 '21 at 13:07
11

Adding that flag does not fix it for me on IntelliJ 2020.3.2 Ultimate – Jire Feb 24 '21 at 18:01
4

@Giorgi Tsiklauri, in the latest IntelliJ version, the settings is now under _File | Settings | Build, Execution, Deployment | Compiler | Shared build process VM options_. It works for me. For your question about what does it mean, this issue happens only when you get some annotation processor like Lombok and is linked to the way IntelliJ handle incremental recompilation for what I understand. Why this option is not set by default? That is the question… – Doc Davluz Mar 04 '21 at 08:40
@DocDavluz - "*issue happens only when you get some annotation processor like Lombok*" - wrong. – Giorgi Tsiklauri Apr 19 '21 at 07:44
2

Working with IntelliJ 2021.1 version but after adding that flag IntelliJ should be reloaded and you should also run `mvn celan & install` in case of maven project. – Falcon Apr 21 '21 at 09:19

score 22 · Answer 2 · edited Aug 15 '22 at 18:20

I was using an older version of Lombok, changing to newer version fixed the issue in IntelliJ

Old version:

<dependency>
    <groupId>org.projectlombok</groupId>
    <artifactId>lombok</artifactId>
    <optional>true</optional>
</dependency>

New version:

<dependency>
    <groupId>org.projectlombok</groupId>
    <artifactId>lombok</artifactId>
    <version>1.18.20</version>
    <scope>provided</scope>
</dependency>

score 8 · Answer 3 · answered Jul 12 '21 at 19:27

8

In my case i was trying to use an old version lombok plugin (version 1.16.16), but it's an old plugin version, I updated to 1.18.20 (obs.: today is july 2021) and it works well.

answered Jul 12 '21 at 19:27

Guilherme Almeida

81
1
1

score 3 · Answer 4 · answered Apr 21 '21 at 22:39

3

I had to remove the target dir with rm -Rf ./target or mvn clean, then inside IntelliJIDEA's Maven panel, I clicked on the Icon "Reload all maven projects". I also tried to "Invalidate cache and restart". Not sure what was working but it solved my error.

answered Apr 21 '21 at 22:39

Karl.S

2,294
1
26
33

I think this has nothing to do with the warning mentioned in the question.. problem arises at the compile time.. and `mvn clean` will just remove built directory. – Giorgi Tsiklauri Apr 28 '21 at 11:38
@GiorgiTsiklauri it does, since I had several times the exact same problem as described in the issue, and each time I solved it by doing one of the mentioned actions. Also it should be linked to IntelliJ only as I don't remember having this problem while running directly `mvn compile`. – Karl.S Apr 28 '21 at 17:42
No, it does not. `mvn clean` does nothing, but just removing the built project directory, which, in case of Maven project, happens to be `target`..so both of your actions do identical job. "*Also it should be linked to IntelliJ only*" - and the question is about IntelliJ only.. have s look at it.. see the tag of the question. – Giorgi Tsiklauri May 03 '21 at 06:16
1

It worked in my case. Thanks – Murad Hajiyev Apr 27 '22 at 01:08

score 2 · Answer 5 · answered Feb 10 '23 at 11:11

2

I know the thread is almost 2 years old, but since this came up in search.

Fo me it worked after File->'Invalidate Caches...'

answered Feb 10 '23 at 11:11

Becker Syd

21
2

score 1 · Answer 6 · answered May 13 '21 at 01:57

1

We can do all operations in IntelliJ IDEA.

add -Djps.track.ap.dependencies=false in proper place.
In the right of IDEA, click Maven -> Reload All Maven Projects.
Also in the Maven -> Excute Maven Goal (represented by a 'm' icon) -> mvn clean -> enter
Then Excute Maven Goal -> mvn install -> enter
Build -> Rebuild Project.

Thank Andrey, djangofan and Falcon.

answered May 13 '21 at 01:57

lyx3030

35
1

7

What do you mean by this point add -Djps.track.ap.dependencies=false in proper place? – Software Engineer Aug 07 '21 at 07:22
1

@SoftwareEngineer Add `-Djps.track.ap.dependencies=false` in the setting "Shared build process VM options:" – red May 06 '22 at 14:13

score 1 · Answer 7 · answered Apr 24 '22 at 08:27

1.New version added in pom.xml

enter code here
<dependency>
        <groupId>org.projectlombok</groupId>
        <artifactId>lombok</artifactId>
        <version>1.18.20</version>
        <scope>provided</scope>
</dependency>
enter code here

2.mvn clean -> build project

score 1 · Answer 8 · answered May 10 '23 at 09:26

In my case, In my case, upgrading the version of the Lombok package did not work.

    <dependency>
        <groupId>org.projectlombok</groupId>
        <artifactId>lombok</artifactId>
        <version>1.18.26</version>
    </dependency>

it still shows the same error.

Parsing java... [applicationname]
java: JPS incremental annotation processing is disabled. Compilation results on partial recompilation may be inaccurate.
Use build process "jps.track.ap.dependencies" VM flag to enable/disable incremental annotation processing environment.
Writing classes

The compiler in the idea perferences panel adds the -Djps.track.ap.dependencies=false parameter.

it didn't work again.

I suspect the cache problem or something, I use the invalid cache under the file and restart it several times, but it doesn’t work.

Finally, the build runner turns on the delegate ide build/run actions to maven, and that's it. However, after it is turned on, it will be very slow when I run the project debug locally, and then turn it off again. Lombok did not report an error, so it was solved.

score 0 · Answer 9 · answered Jun 15 '21 at 09:31

0

In my case,the specific error is couldn't find one class file. I open it and find the suffix magically becomes '.aj'. Change it back to '.java'. It works for me.

answered Jun 15 '21 at 09:31

张秋峰

11
3

Deepak · Answer 10 · 2023-06-04T12:43:43.353

0

This problem also comes when there is non compatible version of java installed on your system .

For my case i was working on debian Linux distro on Ubuntu 22.04 LTS but i installed ARM64 Compressed Archive

When i uninstalled above and installed x64 Compressed Archive

problem was solved .

In this case mvn --version did not worked either and was giving exec path error

edited Jun 04 '23 at 12:43

answered Jun 03 '23 at 10:58

Deepak

2,287
1
23
30

JPS incremental annotation processing is disabled. Compilation results on partial recompilation may be inaccurate

10 Answers10

Linked