<hans> There are now two tasks:
<hans> task exec(type: Exec) { ... }
<lg_jp> Which ticket is that from?
<hans> task java(type: Javaexec) { classpath = configurations.compile ... }
<hans> As well as methods:
<hans> exec { ... } and javaexec { ... }
<lg_jp> Awesome, we needed those tasks. Are they added to the Java plugin then?
<hans> Yes.
<lg_jp> task java(type: Javaexec) { classpath = configurations.compile ... } shouldn't that be configurations.runtime ?
<hans> It usually should :)
<lg_jp> :)
<lg_jp> You're right.
<lg_jp> Hm... I wonder if this will make plugins easier in some cases.
<lg_jp> Maybe not because most of the things have ant tasks
<lg_jp> Do these fork into their own JVM process?
<hans> Yes.
<hans> It is just more convenient then the Ant tasks.
<hans> Specially the handling of the output.
<lg_jp> Sure.
<lg_jp> Ah, very true.
<hans> With Ant you had to use the output properties of the Ant task.
<hans> With the new stuff by default standard out is shown on the console.
<hans> But you can redirect it to any other log level easily.