Open kchaber opened 3 weeks ago
Currently, the asyncapi-core uses the lombok dependency in the default/compile maven scope. This results in having the lombok dependency in the final jar, which can cause various compile problems in projects using the asyncapi.
asyncapi-core
lombok
<!-- Code generation --> <dependency> <groupId>org.projectlombok</groupId> <artifactId>lombok</artifactId> </dependency>
As per lombok docs the lombok dependency should be marked as provided
provided
<!-- Code generation --> <dependency> <groupId>org.projectlombok</groupId> <artifactId>lombok</artifactId> <scope>provided<scope> </dependency>
N/A
None
Describe the bug.
Currently, the
asyncapi-core
uses thelombok
dependency in the default/compile maven scope. This results in having the lombok dependency in the final jar, which can cause various compile problems in projects using the asyncapi.Expected behavior
As per lombok docs the
lombok
dependency should be marked asprovided
Screenshots
N/A
How to Reproduce
lombok
is present in the final jar🥦 Browser
None
👀 Have you checked for similar open issues?
🏢 Have you read the Contributing Guidelines?
Are you willing to work on this issue ?
None