Hmm, I was afraid of that. I figured I'd adjust it programmatically, and discovered two things that do not seem possible at the moment by using the LoggingManager:
1. Doesn't seem to be a getLogLevel to determine what the current level is. 2. Doesn't seem to have a way to turn off all logging (no LogLevel.OFF) Also, I cannot seem to easily grab the logger that is wrapped around Ivy, as adjusting the task logger for the task where .resolve() is being called doesn't have any effect. -Spencer --- On Wed, 2/9/11, Peter Niederwieser <[email protected]> wrote: From: Peter Niederwieser <[email protected]> Subject: [gradle-user] Re: Test whether configuration resolves without warnings displayed? To: [email protected] Date: Wednesday, February 9, 2011, 11:31 AM This warning gets logged by Ivy. I don't know of a way to get rid of it other than setting Gradle's log level to quiet, either always or temporarily. Maybe we should make the mapping from Ivy to Gradle log levels configurable. Seems like a natural extension of Gradle's otherwise very flexible logging system. -- Peter Niederwieser Developer, Gradle http://www.gradle.org Trainer & Consultant, Gradle Inc. http://www.gradle.biz Creator, Spock Framework http://spockframework.org ____________________________________________________________________________________ Get your own web address. Have a HUGE year through Yahoo! Small Business. http://smallbusiness.yahoo.com/domains/?p=BESTDEAL
