The option thin.libs puts jars at the end of the classpath instead of the front

[werner77]

To be able to override dependencies it would make a lot of sense to put them in front of the classpath.

[dsyer]

I don't like to rely on classpath ordering. It's a slippery slope. Wouldn't it be better to just change the version of an existing dependency? I'm trying to think of a scenario where I would want to put the extra dependencies first on the classpath and I can't see one yet.