Russel Winder wrote:
I just spotted Adam put up GRADLE-423. I was unsure whether to post on
the issue or on the email list. I thought I would start here, I can
always copy stuff there later.
Whilst it would be good to have a nice consistent Gradle way of doing
things for includes and excludes, I wonder if there is benefit in doing
an *and* approach rather than just an *or*. What I mean here is provide
a globally consistent Gradle approach *and* allow each of the "tasks" to
be specified in the way Ant tasks do -- so that people coming to Gradle
from Ant can do more of a transliteration of their current build specs.
I think the *and* approach would be good.
The idea here is that people will be transitioning to Gradle from Ant
and Maven and will be looking for ways of translating their current Ant
scripts and POMs to Gradle equivalents.
I continually get people saying "I am moving from Ant to Gant" who are
trying to transliterate their builds, people are not re-writing from
scratch.
(And yes I always mention that they may want to go straight to Gradle
and not work with Gant at all.)
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
