-
Notifications
You must be signed in to change notification settings - Fork 146
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
Release YamlBeans to Maven Central? #169
Comments
Someone else was handling Maven releases, but they seem to be gone now. Someone needs to take it over. I've never done it and when I tried many years ago, in the early days of Maven, the process was terrible. Maybe it's better now? Possibly made more complex by needing to take over the task from someone else. FWIW, I did a 1.17 GH release yesterday. We could attach a JAR from it, for people managing dependencies the old fashioned way. |
Fork was done in https://github.com/Contrast-Security-OSS/yamlbeans |
anyone can push it to Maven Central? |
anyone can release a JAR as binary? |
@NathanSweet said they could attach JAR to the release, but right now it is not there yet. One can build one, but I think the "safest" would be to attach one to the release page |
I've attached the 1.17 JAR: |
I see that the latest version on Maven Central is 1.15, but GitHub has tags for 1.16 and 1.17. Would it be possible to release 1.17 to Maven Central? That would allow code to use
SafeYamlConfig
.I also see that there is a 1.17 released as
com.contrastsecurity:yamlbeans
a couple of weeks ago, but it would be more reassuring to have something released in thecom.esotericsoftware.yamlbeans
group.The text was updated successfully, but these errors were encountered: