On Tue, 2009-08-25 at 07:26 +0200, Hans Dockter wrote: [ . . . ] > We are still pre 1.0 and I grow more and more unhappy with the term > configuration for something which is usually a classpath. I just took > this term from Ivy because I couldn't think of anything better. But I > think we should try hard to find a better name. Then 'configuration' > would be free.
Configuration management has basically defined a meaning for
configuration, so it would be good if Gradle could be consistent with
that.
If a classpath is a classpath, then why not call it a classpath?
I wonder why Ivy chose the terms it did? Understanding their rationale
might help in sorting out what they got wrong.
--
Russel.
=============================================================================
Dr Russel Winder Partner
xmpp: [email protected]
Concertant LLP t: +44 20 7585 2200, +44 20 7193 9203
41 Buckmaster Road, f: +44 8700 516 084 voip: sip:[email protected]
London SW11 1EN, UK m: +44 7770 465 077 skype: russel_winder
signature.asc
Description: This is a digitally signed message part
