rturner-edjuster commented on issue #144: URL: https://github.com/apache/logging-log4j-kotlin/issues/144#issuecomment-4068906321
@vy We are a low-usage user and it would not be hard for us to convert back to the Java API for our affected projects. Ironically all the changes are "ready" in the main branch and it would just need to be released publically. I think the problem actually stems from changes in the main implementation and not the API itself, which like you said is concerning. Having said that, it would also likely get released more often if it was part of the main project, and not off on it's own. I doubt it's much effort to "maintain" if it's part of the main project. I cannot shed more light on the possibilities -- although I did wait a while before reporting it, assuming someone would have dealt with it long since. In reality, the Java API is largely sufficient when running on the JVM. If we we native or using another target, the current API would of course be insufficient as it's only the API and not the whole stack, so it doesn't really fulfill the needs of a full Kotlin solution. -- 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. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
