but I also like the idea of supporting it at a global level

an extension function to String could do the trick but might not be the best option

Global exclude would work fine for me right now... that's how the manual work-around worked. Not sure what other use-cases exist

it does

say you have an app that depends on two jars that depend on different versions of gson

you could simply exclude one dependency to gson from one of the jars

Good point. I thought that was somehow magically handled by Kobalt already -- by looking at major/minor versions i guessed.

that could be an option (and I do not know if it does exist) but as a developer I would like to also have the control to choose which version stays and which goes.

So, if Kobalt and Maven use exactly the versions specified in the pom's/Build.kt, excluding dependencies more granularly may be pretty useful

maven allows it

not sure about gradle

@cedric i updated to .379 but get this:

/private/var/folders/gk/ml0b8m817tg8wg0my3819tnc0000gn/T/kobalt734211128164466195.kt:32:9: error: unresolved reference: exclude
        exclude("org.slf4j:slf4j-simple:1.7.5")
        ^
*****
***** ERROR Could not compile Modified Build.kt
*****

Show me your full build

@pabl0rg: Oh I called it

excluded

by accident. Try that, but I’ll change it to

exclude

in the next version

Actually I’m not sure which one makes more sense

sometimes I use the infinitive (

compile

), sometimes past (

provided

) and sometimes a noun (

runtime

)

Totally inconsistent, but that’s how gradle does it too

I prefer

exclude

since it sounds like a command to the build

@bmsantos: Even with the (current) global exclude, you can exclude a very specific version and just that one

Ok I’ll change it in 380

humm.. then that might just be enough then

does it remove dupes?

Actually it seems better than local one: if you want to exclude a specific version, you want to exclude it everywhere, not just as a subdependency of one of your dependencies

correct

Yes, dupes are removed by kobalt and it only keeps the highest version it finds (outside of exclusions)

sold!

Deploying 380

Downloaded .380 and exclude worked great!

Aside from mixed (java/kotlin) compilation and plugins that we users should contribute (proguard?), what useful features does gradle have that kobalt doesn't? (i'm not a gradle user)