Hmm. Well, it looks like Gradle is using SLF4J under the hood, and I didn't
see any log4j, so I'm assuming it's using JDK Logging.
However, I've tried to set the logging levels to "ERROR" and it still
doesn't seem to reduce the output at all.
[snippet src="logging.properties"]
.level = ERROR
org.gradle.logging.ProgressLoggingBridge.level = ERROR
org.gradle.api.Project.level = ERROR
[/snippet]
Then you can tell Gradle to take these logging properties via a command line
arg:
[command]
gradle clean build -Djava.util.logging.config.file=logging.properties
[/command]
I can see that the logging properties are working by adding this to my
build.gradle file:
[code src="build.gradle"]
import org.gradle.api.logging.Logger
import org.gradle.api.logging.Logging
import org.gradle.logging.ProgressLoggingBridge
Logger LOGGER = Logging.getLogger(ProgressLoggingBridge.class)
LOGGER.debug("DEBUG")
LOGGER.info("INFO")
LOGGER.error("ERROR")
// use project logger
logger.debug("PROJECT - DEBUG")
logger.info("PROJECT - INFO")
logger.error("PROJECT - ERROR")
[/code]
Running executing the script will only print out "ERROR", and "PROJECT -
ERROR".
So, I'm guessing that the output that you're seeing is actually going out
via system.out, and not a logger. Not sure how to turn that off without
turning off all output.
On Tue, Sep 7, 2010 at 11:53 PM, Rene Groeschke <[email protected]> wrote:
> Hi Eric,
> well 'q' removes all output. That is a bit too few infos. I would like to
> have infos about resolving artifacts (Downloading etc.), but remove the
> status messages (Loading, Building.
>
> regards,
> René
>
--
Learn from the past. Live in the present. Plan for the future.
Blog: http://www.townsfolkdesigns.com/blogs/elberry
jEdit <http://www.jedit.org> - Programmer's Text Editor
Bazaar <http://bazaar.canonical.com> - Version Control for Humans
