We're working on both an Idea and a TeamCity plugin for running gradle. One of
the complexities we're having is getting runtime information back from gradle
while executing. While we can get the information we need, it requires doing
some work that could be simplified. Adding a single 'Execution Listener'
(similar in spirit to the AntBuilderListener) that provides the following would
not only aid our development, but help future gradle plugins. I propose a
single Execution Listener interface made up of the following:
- All the information provided by BuildListener.
- All the information provided by TaskExecutionListener
- Easy access to the logged information (with the order of callbacks easily
associated with the above callbacks).
Currently, getting this information requires adding multiple listeners at
different times. For example, you have to wait for
BuildListener.taskGraphPopulated to add a TaskExecutionListener. And hooking
into Log4J can be error prone if you don't setup things just right. Building
this into gradle provides an easy way for any developer to get the most common
information they would need to integrate gradle into other IDEs and CI servers.
Ultimately, we would want some way to add an external listener via the command
line similar to Ant's "-listener", but didn't want to go into that until the
listener itself was agreed upon.
Mike
Automated Logic Research Team
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
