Kobalt: http://beust.com/kobalt
What needs to be done:
kobalt/src/Build.kt./kobaltw installkobaltBuild/libs and put those in your maven repoThanks!
/cc @sanity
Hi
Is there a way for to install the libs in the local maven repo as well?
@jitpack-io By "local maven repo", do you mean the repo cache (Maven puts it in ~/.m2/repository, Kobalt in ~/.kobalt/repository) or a local running instance such as artifactory?
Just the ~/.m2/repository but ~/.kobalt/repository would do as well.
No, install doesn't do that. Nor should it: these cache directories are only touched by the build tool (whether it be gradle or kobalt). If Kobalt encounters this dependency in a build file, then it will download that artifact in the cache directory.
Do you need the artifacts to be in these cache directories?
~/.m2/repository would be the simplest since that's how JitPack finds artifacts from other build tools.
Just wanted to check in on this
cc: @cbeust @jitpack-io
Hi @sanity
There's really just one small issue. JitPack was designed to pick up artifacts from ~/.m2/repository so making it pick up kobaltBuild/libs is an internal change. Not saying it can't be done but there are priorities.
If anyone has a script/lib that can publish kobaltBuild/libs to ~/.m2 then that'd be the quickest way to support kobalt.
I think the maven repository problem can be fixed by including @ethauvin plugin https://github.com/ethauvin/kobalt-maven-local
I managed to publish this project with jitpack and use it from another project with full success. In summary, I used @ethauvin's plugin and added this jitpack.yml
install:
- echo "Running kobalt publishToMavenLocal"
- rm -rf .kobalt/build
- ./kobaltw --log 2 clean publishToMavenLocal
Same, I haven't had any issues jitpack the few times I tried. Please reopen if you have an example that doesn't work.
Most helpful comment
I managed to publish this project with jitpack and use it from another project with full success. In summary, I used @ethauvin's plugin and added this
jitpack.ymlthis is the resulting build log