[logback-user] What support is needed to run with logback.groovy configuration?

Steve Cohen scohen at javactivity.org
Sat Jul 28 19:20:14 CEST 2012


No, I hadn't, thanks!  That works.
I made groovy a runtime dependency and it works.

My repo mirror only showed me groovy up to 1.6.3, but when I changed it 
to 1.7.2, it found it and it works.





On 07/27/2012 05:09 PM, ceki wrote:
>
> Hi Steve,
>
> Have you tried adding the following?
>
> <dependency>
> <groupId>org.codehaus.groovy</groupId>
> <artifactId>groovy-all</artifactId>
> <version>1.7.2</version>
> </dependency>
>
> It's the groovy dependency that logback-classic uses.
>
> HTH,
>
> On 27.07.2012 17:54, Steve Cohen wrote:
>> I switched my application from using logback.xml to using
>> logback.groovy. I just wanted to try it but off the bat, I much prefer
>> scanning through an easily alphabetized list of loggers in the groovy
>> file to the mess that you get with XML and lots of loggers.
>>
>> However, my hopes for a quick success were dashed when I saw:
>>
>> Groovy classes are not available on the class path. ABORTING
>> INITIALIZION.
>>
>> What must I do to my application classpath to allow logback
>> configuration via groovy? The manual does not seem to have any
>> information on this.
>>
>> Also, I noticed via goggling the issue that JSON causes an issue with
>> groovy. This will also impact me as our application makes use of JSON.
>>
>> Thanks to anyone who can provide this information.
>>
>> Steve Cohen
>
>



More information about the Logback-user mailing list