magik 0.2.7 released <https://github.com/elect86/m...
# opensource
e
magik 0.2.7 released https://github.com/elect86/magik it's a Gradle plugin to publish on and use a Github repository as a maven repository
it should work also with Groovy buildscripts now, but I'd like to get some feedbacks
d
Oooh, that's pretty cool.
e
rather than commit binaries to git, have you considered building a proxy which translates to binaries attached to GitHub releases or filled served directly from ghcr (like homebrew does)?
e
if one doesn't publish fat jar, the binaries remain relatively small. I did thought shortly about that, but I was looking for a truly flexible, free and without authentication to consume maven repository
also, I don't have idea how to make it up for the missing maven config files
thinking about it, it might be doable if a user uploads to the release all the files one would normally publish
p
Sounds amaizing
e
@ephemient one problem was (and is) that the url is not something you can programmatically figure it out easily, ex: https://github-registry-files.githubusercontent.com/265301594/bd659e80-85ae-11ec-9c84-92c4aaabcc58[…]esponse-content-type=application%2Foctet-stream on https://github.com/jcansdale-test/gradle-java-publish/packages/245399 with github you can easily access everyfile through the
raw
url counterpart..
l
The i in "GitHub" should be lowercase in the two tagline. Cool stuff BTW
e
ok, so this is on you, @ephemient What you said made me thinking again and I came out with a solution/compromise for Github Packages. With a
credentials
file in the root project, now Magik can let clients automatically fetch packages without the hassle to authenticate themselves manually The first option remains still better, imho
l
Still in the tagline: M~A~ven & Git~h~ub -> a & H
e
it's where the magik comes from
l
Oh! My suggestion: Maven Artifacts on GitHub for Kotlin. I think it'd be more noticeable.
e
deal
(but I still need the i) 🙂
l
International
Incredible
e
done, but the upper H would ruin everything 😛