On Aug 25, 2009, at 11:02 AM, Russel Winder wrote:
On Tue, 2009-08-25 at 08:36 +0200, Tomek Kaczanowski wrote:
Hi Hans,
I know that this would be a pretty disruptive change.
It would have been much better to have done this earlier. But
that's why we are still pre 1.0.
It is definitely NOT too late ! It is much better to change it now,
than to stick with this confusing term for ages.
BTW. "paths" sounds good to me
As long as 1.0 is not out then change is more or less expected, and
not
really a problem if announced and marketed. Once 1.0 is reached
then it
becomes difficult to begin to change nomenclature -- until 2.0 of
course, but even then it is hard.
My two pennyworth is that there is a tension here: on the one hand
having a nice consistent, orthogonal labeling of concepts makes it
easier for people to work with and to learn, on the other hand
Gradle is
an adapter on Ivy and so should follow the Ivy labelling -- to have to
have a look up table for the labels of concepts Ivy <-> Gradle could
be
irritating. On the third had, Gradle has already created something
of a
tension by having a different labelling compared to both Ant and
Maven,
so it is setting up as the "third way", which leads back to going with
change to make sure the concepts are clearly, consistently, and
orthogonally labelled.
We need to find the best terms in the context of Gradle. Of course, in
case all other things being equal, we prefer established terms.
I wonder what Buildr has done here?
They don't have this concept.
- Hans
--
Hans Dockter
Gradle Project Manager
http://www.gradle.org
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email