-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Please upload v0.1.2 to Maven Central #14
Comments
Hello @airbrake, Do you have any plan to release this library version on Maven Central as asked in the previous comment? Thanks |
Hi 👋 I was doing some tests yesterday and it turns out airbrake-logback v0.1.1 is not compatible, not just with JDK 17, but also with any of the airbrake-javabrake 0.2.x nor 0.3.0 versions released in the last five years, because airbrake-logback v0.1.1 is using a
This forces me to use airbrake-javabrake v0.1.6 which as I said is more than 5 years old, and I don't even know if it's still fully compatible with Airbrake's current API. All of this is of course solved in airbrake-logback v0.1.2 (that's why I'm writing a comment here instead of opening a new issue). Even the README tells us to use v0.1.2 but, as @thibaut-wed and @cohei mentioned, v0.1.2 is not available on Maven so we cannot use it. We are getting some pressure to just switch to airbrake-log4javabrake2 which AFAIK doesn't suffer from any of this problems, but we'd really like to stay with Logback as that's what we use in most of our services. We would really appreciate it if you could just release v0.1.2 to Maven Central. Thanks in advance. PS: tagging @sumitjoshi1989 as v0.1.2 committer, @mmcdaris as v0.1.2 reviewer and approver, and @thompiler as the one who deleted the already-merged |
OK, I'll add it. |
Apologies for the delay on this one. The release slipped through the cracks. We now see v0.1.2 live on mvn repository. |
Thanks a lot! |
https://mvnrepository.com/artifact/io.airbrake/logback
Hi,
I think v0.1.2 is not available because it's not on Maven Central.
fixes: #9 #12 (comment)
The text was updated successfully, but these errors were encountered: