How about not printing UP-TO-DATE tasks during a normal build?

Old Forum
1

During a normal build most of my tasks are usually UP-TO-DATE and proudly say so during the build process.

I was wondering if it wouldn’t make sense to only report tasks that are actually executed, i.e. tasks that are not UP-TO-DATE? The current behavior could be a more verbose mode that one could toggle on if desired.

The only downside I can think of at the moment is that this could potentially confuse new users. They could assume that nothing is executed because something is wrong with the build…

2

I’v started using the following script (I call it ‘g’) to invoke gradle:

#! /bin/bash

gradle --daemon $* | egrep --color=always -v ‘UP-TO-DATE|SKIPPED’

It means I can run gradle in a much smaller ‘konsole’ tile and have a lot of space to watch the logs as gradle deploys my applications.