[GRADLE-3] Add Visitor or Listener interfaces to the core domain model where it makes sense Created: 13/Feb/08  Updated: 04/Jan/13  Resolved: 08/Feb/09

Status: Resolved
Project: Gradle
Affects Version/s: 0.1
Fix Version/s: 0.5

Type: New Feature
Reporter: Steven Devijver Assignee: Hans Dockter
Resolution: Fixed Votes: 0

Issue Links:
dependent on GRADLE-163 Offer afterDagCreated listener Resolved
dependent on GRADLE-250 Improve error reporting when a listen... Resolved
dependent on GRADLE-251 BuildListener is notified of completi... Resolved
dependent on GRADLE-302 Add a listener which is notified as t... Resolved


For example, there could be a Listener that gets called on successful or failed configuration file access, like gradlesettings.groovy and gradle.groovy.

Other options are before and after a task gets executed, ... .

Comment by Jon Cox [ 22/Jan/09 ]

Can you give a nice practical example of what you'd do with something like that?

Comment by Hans Dockter [ 08/Feb/09 ]

See the issues this issue depends on. We can close this general issue.

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