Closed rocketraman closed 3 years ago
Seems like a good idea. Are there CI updates needed here, though? Some build failure.
Seems like a good idea. Are there CI updates needed here, though? Some build failure.
Weird I'm not seeing any errors in the build logs, just the abort at the end. Can we try to rebuild it?
If you don't have a "re-run" link on the GitHub Check, then try adding an empty commit or possibly closing then reopening the PR to retrigger CI.
@jvz No idea why CI is failing but its not limited to this branch. The other PRs I recently submitted failed with the same non-error.
@jvz Not sure what was up with the CI system before, but it seems to be working now. I added a couple of extra commits on this branch.
I'm not blocking you from merging this. Feel free :)
Following the discussion in https://github.com/apache/logging-log4j-kotlin/pull/14, I believe the best path forward is to make the Kotlin dependences "provided" dependencies, which should prevent downstream projects from pulling in older versions of Kotlin libs transitively.
However, see the first commit's message -- it scares me a bit because kotlin-reflect and possible the coroutines dependencies may not be on everyone's classpath, and this will cause a runtime failure. I'm not sure what the best approach is but opening this PR for discussion.