Re: [gradle-dev] Changing the name for configurations

[Hans Dockter]

On Aug 26, 2009, at 2:36 PM, Steve Appling wrote:

I would love to change this name.  I did not come from an Ivy  
background and have always felt this was awkward.

I have also always felt that using configurations to store paths and  
to specify a distribution archive were two very different uses that  
didn't belong together.   I would like to see the archive part  
pulled out into another concept.

To me, the core of configurations are named dependencies.  I like:

dependencyNames {
  compile
  openAPI
}

dependencies {
  compile 'commons-io:commons-io:1.4'
}

I think "paths" are a little too generic.  And paths.compile.asPath  
seems a little strange :)

If we call it paths, we could replace asPath with the toString method.  
We don't have two different concepts here which share the same name.

- Hans

--
Hans Dockter
Gradle Project Manager
http://www.gradle.org


---------------------------------------------------------------------
To unsubscribe from this list, please visit:

   http://xircles.codehaus.org/manage_email