@User uploaded a file:

Yeah, that works for most.

@cedric Doesn't

autoGitTag

work in

bintrayUpload

?

Ah I knew I had something like that but couldn't remember

@cedric Any problems if I change it to

autoGitTag(true, "message")

?

or adding

gitTagMessage

?

or even

autoGitTag(true, "tag" , "message")

with tag defaulting to

project.version

?

Quick question, if I want to make use of Kobalt on other platforms that doesn't have homebrew, the manual install and manual update is the only way currently?

@janvladimirmostert Yes. I use it on Windows and MacOS so far, I'm open to other options

e.g. chocolatey on Windows or sdkman (although I had a few issues with that one)

My build system is running on Debian, would Kobalt run in Debian as well ?

Most definitely

Awesome!

Let me know what I can do to help installation on Linux, I don't test much there since I don't have a machine

I'll play around a bit and see how it works and report any issues.

Awesome, keep me posted

@janvladimirmostert you may find this gist helpful https://gist.github.com/pabl0rg/a17fb4c8c3c3b57eb2833f2125c2b502

@cedric or @ethauvin can you explain to me how Kobalt loads plugins? I mean, how can we import symbols from a package that a plugin contains before we've downloaded the plugin's jar? I see there's some parsing of the build file happening.

I guess Kobalt parses the build file, resolves and downloads plugins, and then compiles the build file and runs it. Is that right?

I'm trying to compile your fork of u2020 using kobalt. I've updated to 1.0.8 but it dies an early death saying

*****
***** ERROR Couldn't compile file: import com.beust.kobalt.plugin.android.*
/private/var/folders/gk/ml0b8m817tg8wg0my3819tnc0000gn/T/kobalt1697658814156817287/Build.kt:7:32 Unresolved reference: android
*****

I worked around that problem by going into a different project (that uses no plugins) and doing ./kobaltw --resolve com.beustkobalt android0.97

then I hit another. looks like the retrolambda plugin is too outdated. i sent at PR

@pabl0rg Any more questions after the emails we exchanged?

Only one: how can I build u2020 with kobalt? (they asked for a demo)

Do you have my fork of it?

yes

It's not building?

no

OK I'll have to take a look

1. its using

kobalt.version=0.385

which depends on an obsolete (not available) version of the kotlin compiler