[
https://issues.apache.org/jira/browse/GOBBLIN-1226?focusedWorklogId=471560&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-471560
]
ASF GitHub Bot logged work on GOBBLIN-1226:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 17/Aug/20 16:51
Start Date: 17/Aug/20 16:51
Worklog Time Spent: 10m
Work Description: sv2000 commented on pull request #3072:
URL:
https://github.com/apache/incubator-gobblin/pull/3072#issuecomment-674992283
@hkoosha Thanks for this valuable contribution. Hope, this triggers a more
comprehensive discussion about recommended usage of Lombok. To that end, it
would be great if you can cite references/enumerate specific issues associated
with usage of Lombok as a runtime dependency. This should be educational for
the wider Gobblin developer community.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 471560)
Time Spent: 1h 20m (was: 1h 10m)
> Lombok should not leak into runtime dependencies.
> -------------------------------------------------
>
> Key: GOBBLIN-1226
> URL: https://issues.apache.org/jira/browse/GOBBLIN-1226
> Project: Apache Gobblin
> Issue Type: Bug
> Reporter: Koosha Hosseiny
> Priority: Trivial
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> Lombok is a cool tool (although IMHO not worth it's troubles, considering
> generated code is harder to debug, incompatibilities in bytecode, line
> version mismatch in debugger, etc, etc) which promises to have zero runtime
> dependencies.
> It is also *strongly* advised by its developers that it should be present on
> the classpath only during compilation/code generation and _not at all_,
> during runtime. (I don't have an exact reference at hand but it can be
> searched in the lombok google forum).
> Lombok in runtime's classpath is considered not only a bad practice but wrong
> usage of lombok.
> The issue it caused me was that it brings an older version of guava into path.
> I propose the `compile ...lombok` in `build.gradle` be changed to
> `compileOnly`. This has zero effects on any current project using gobblin.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
