but if your library was built using kobalt, I don't think jitpack would work - right?

Let me make sure I understand jitpack correctly

My understanding: you tell jitpack your github location, it pulls your project, builds it and exposes it as a maven repo. If you just add

val r = repos(”<http://jitpack.io>”)

to your

Build.kt

, kobalt should be fine

ah, yes, that's if you want to use a jitpack repo from kobalt, but what if you want to build a library with kobalt and have jitpack pull the project, build it using kobalt, and then publish the artifact

But jitpack pulls from github, you never push directly to jitpack (I think?)

eg. here is a project of mine (where I use maven) that is built and published via jitpack https://jitpack.io/#sanity/quickml

So you can push to jitpack?

jitpack pulls from github on-demand, so simply trying to download an artifact from jitpack will cause it to pull from github and do its thing

Right so there is no build system in the equation, correct?

You build locally using whatever and push to github.

well, jitpack needs to built the artifact

oh

got it

Sorry I haven’t had my coffee yet simple smile

but if there could be a gradle "wrapper" for kobalt, then that would work without modification to jitpack, i don't know if that would be possible

or we just keep pestering jitpack until they support kobalt directly simple smile

Probably easier to ask jitpack to detect the Kobalt file and in that case, issue a

./kobaltw assemble

(like they probably already do for gradle)

yes, i'll ask them - they're fairly cooperative in my experience, good guys

It would be trivial to write a gradle plug-in that invokes Kobalt but it’s a bit hacky simple smile

i'm afraid I need to go, but will be back in a few hours, really excited about this project, gradle kinda sucks and maven really sucks simple smile

(besides, jitpack would probably not know about this plug-in and how to invoke it anyway)

Alright, keep me posted how it goes!

oh, one final note, from the perspective of a first-time user, you might want to iterate a little on the "quickstart" - particularly in terms of how to start a new project, but also kobaltizing an existing project - I found myself worrying a bit about whether it's going to be a PITA to get it to play nice with IDEA (which, of course, has mature support for Gradle and Maven)

I'm not saying that it is or will be a problem, I just found myself being nervous that it might be

Yes, it’s an important step, do you have any specific suggestions to improve it?

maybe a walkthough including screenshots of how to set it up with IDEA (since, I expect, 100% of your early userbase will be IDEA users)

or a screencast

I’ve thought about a screencast, it’s a good idea

I also find it a little annoying to have to set environment variables (or, at least that the documentation suggests that it is necessary to set environment variables) - I don't recall that being necessary with gradle

anyway, now I'm late so I really need to run simple smile ttyl