we can turn off our private CI for auto building and now everyone can look at the actual build results
@Dinnerbone
It may be the time to move to Maven Central as a binary repository (as discussed in Twitter) which will be comparatively easy and will let more libraries depend on Brigadier without any problems.
The downside of using libraries.minecraft.net is that it limits those using binaries from there in deploying their own projects to Central as (according to rules) no custom repositories can occur in project build configuration if publishing there.
As for now it seems the right moment when migration won't be hard.
The recommended sollution is making Travis perform deployment when the branch is master and (recommended) when the commit is tagged.
I may take the control over this if the PR gets positive feedback. As of requirements someone will have to generate some RSA keys to sign binaries.
Some research showed that Maven Central does not require this now and allows deployment of third-party-repo-dependent artifacts. But this issue still seems to be useful.
As now only Travis is used for CI
It may be the time to move to Maven Central as a binary repository (as discussed in Twitter) which will be comparatively easy and will let more libraries depend on Brigadier without any problems.
The downside of using
libraries.minecraft.net
is that it limits those using binaries from there in deploying their own projects to Central as (according to rules) no custom repositories can occur in project build configuration if publishing there.As for now it seems the right moment when migration won't be hard. The recommended sollution is making Travis perform deployment when the branch is
master
and (recommended) when the commit is tagged. I may take the control over this if the PR gets positive feedback. As of requirements someone will have to generate some RSA keys to sign binaries.