@Slf4j support reports an error

Short description

i had to upgrade to intellij 2018.2, and i am using plugin version 0.19-LATEST-EAP-SNAPSHOT

I have a class annotated with @Slf4j annotation, and the following code: log.warn("Extra page of books of library {} genre {} author: {}", library, genre, author);

The IDE marks this line as error - Wrong 1st argument type - Found 'java.lang.string, required: ‘org.slf4j.marker…’

Expected behavior

Error should not appear.

Version information

No error

• IDEA Version: Please provide full IntelliJ IDEA Version - available from About view intellij 2018.2
• JDK Version: What is your JDK version, including update level?

java version “1.8.0_171” Java™ SE Runtime Environment (build 1.8.0_171-b11) Java HotSpot™ 64-Bit Server VM (build 25.171-b11, mixed mode)

• OS Type & Version: _Are you on Mac/Windows/Linux? mac
• Lombok Plugin Version: What is the version of the plugin installed?`

0.19-LATEST-EAP-SNAPSHOT

• Lombok Dependency Version: What version of lombok.jar are you using?

Lombok-1.16

Steps to reproduce

What steps do we need to take to reproduce this issue?

1. ???
2. ???
3. ???

Sample project

Please provide a sample project that exhibits the problem. You should also include .idea folder so we can inspect the settings.

• Sample project provided
• I am able to reproduce this error on the sample project by following the steps described above

Additional information

Is there any additional information you can provide to help us understanding and solving the issue?

Stacktrace

If you are experiencing an issue and IntelliJ throws an error please provide the stacktrace.

STACKTRACE HERE (inside code markup)

[sumitdang]

@Override public Optional<List<SamplePojo>> getSamplePojoByParam123(final String param1, final String param2, final String param3) { log.info(“Called - getSamplePojoByParam123({0}, {1}, {2})”, param1, param2, param3);

    log.info("Called - getSamplePojoByParam123({}, {}, {})", param1, param2, param3);

Here is the error -

[Ghilteras]

@mplushnikov I’m still experiencing this issue by the way, can we reopen it?