Thank you for providing the groovyless artifact!

As far as I understand it, Groovy Eclipse has made use of this artifact now in order to provide a new (snapshot) version of the Groovy plugin that no longer creates issues with other Eclipse plugins using logback.

That said, a point was raised that instead of offering a groovy-ful and a groovy-less version of logback, it might be good to consider offering a groovy-less version by default and putting the Gaffer into a separate optional companion artifact. Otherwise, it could e.g. happen that dependency resolving mechanisms such as Maven's would keep both (with and without groovy) versions on the classpath - potentially in different versions - which could lead to the same class being multiple times on the classpath in different versions which in turn might cause unexpected behavior.