[GRADLE-834] UP-TO-DATE message Created: 23/Feb/10  Updated: 12/Jul/16  Resolved: 12/Jul/16

Status: Resolved
Project: Gradle
Affects Version/s: 0.9
Fix Version/s: None

Type: Improvement
Reporter: Philip Crotwell Assignee: Unassigned
Resolution: Fixed Votes: 0


I like the "UP-TO-DATE" messages next to tasks as they execute. Makes it easier to tell if gradle noticed a file change (mostly because I forgot to save the file in eclipse) However, given the variable length of task names, it is hard to see at a glace what is up to date and what isn't. I think it would be clearer if it was a prefix instead of a suffix. A single letter would likely also be sufficient (a la version control). So, perhaps instead of

:TauP:compileJava UP-TO-DATE
:TauP:processResources UP-TO-DATE
:TauP:jar UP-TO-DATE

you would get

U :TauP:compileJava
U :TauP:processResources
U :TauP:jar

Or, perhaps it is better to mark things that are actually done instead of those skipped, so W for "working"??? Also, it might be nice to have F for a failure that doesn't stop the build?

W :TauP:classes

Also, is there a reason that "classes" seems to never be "up to date"?

Comment by Adam Murdoch [ 23/Feb/10 ]

There's no reason, other than we haven't added the 'up-to-date' logic to deal with tasks like 'classes' which just depend on other tasks and do no work themselves. I will add this sometime soon (before a 0.9 release).

Comment by Steve Appling [ 20/Apr/10 ]

While I like the idea of moving the UP-TO-DATE message to a prefix position, I think it is important enough to spell out. I don't like a single letter marker indicating that a task was completely skipped.

Comment by Lóránt Pintér [ 12/Jul/16 ]

This has been fixed some time ago.

Generated at Wed Jun 30 11:40:08 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.