Hi Ross,
On Aug 3, 2009, at 11:24 AM, Ross Black wrote:
Hi,
I am reviving the patch in a git branch: http://github.com/black/gradle-scala/
Cool.
I will initially just get the existing code working again, and then
we can figure out what other changes, and simplifications (as Jeppe
suggested) to apply.
Good plan.
Just a couple of questions:
- if this is to be included in the main gradle code (I assume that
is where it will live until the plugin repository mechanism is
figured out?),
Yes. Although let's see how soon we get some plugin mechanism running.
are you still attempting to have all that code written in Java?
We have discussed this recently and are not sure if this is really a
good strategy.
- I assume use of ant is OK in the short term?
Yes.
I do plan to eventually convert away from use of ant and instead
directly call the Scala compiler api
One thing that we try to achieve is to make our tasks rich and
optimizable. Rich means for example to provide information about the
execution process (e.g. number of classes compiled). Optimizable means
that a task should be able to tell whether it really did some work. If
the task didn't than other tasks might have not do any work as well.
This is harder to achieve when delegating to the Ant tasks. Although
Steve Appling managed to do it for the Javac task (you might have a
look there).
- Hans
--
Hans Dockter
Gradle Project Manager
http://www.gradle.org
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
