My personal opinion is that I really hate this kind of solutions. We will have Gigabytes of binary stuff in repositories for each package. The best would be that all those that use those tetra-kit providers put heads together and help to get the maven/xmvn building to work. With this, even the gradle build will work.
Get the maven artifacts correctly in all dependent packages and have maven building well would be the first step. Then one can bootstrap gradle in the repositories and build the stuff cleanly.
This *-kit solution is only kicking the ball further and making the whole stuff opaque.
Please disable the Publish flags for this package, it is for Build only.
My personal opinion is that I really hate this kind of solutions. We will have Gigabytes of binary stuff in repositories for each package. The best would be that all those that use those tetra-kit providers put heads together and help to get the maven/xmvn building to work. With this, even the gradle build will work. Get the maven artifacts correctly in all dependent packages and have maven building well would be the first step. Then one can bootstrap gradle in the repositories and build the stuff cleanly. This *-kit solution is only kicking the ball further and making the whole stuff opaque.