On Apr 22, 2009, at 2:10 AM, Adam Murdoch wrote:
Hans Dockter wrote:
For 0.6 we will get rid of the default .libs and dists task.
What we will provide is instead is the following:
As in 0.5 the Java plugin adds a number of configurations to the
project. Some are used to retrieve dependencies. Other are used for
artifact handling.
There is the master configuration, to which the default archive is
assigned.
And there is the configuration named 'default' which extends master
and runtime. The default configuration can be used by other
projects to get the classpath of the archives and its runtime
dependencies.
Why do we need 2 configurations for this? Can we get rid of 'master'?
default is the configuration which represents both, the (default)
artifacts produced by the project as well as the dependencies of those
artifacts. It is important to note that resolving the default
configuration with transitive set to false, will still return all
artifacts and the dependencies, but not the transitive dependencies.
This is the way Ivy behaves. Therefore we have another configuration
called master, which just represents the artifacts of the project. As
we have discussed, with the new rich Configuration API it is possible
to access the artifacts only. But not in the normal way you work with
configurations. So I'm not sure if we should get rid of master. What
I'm sure of is, that we need another name if we keep it. :)
- Hans
--
Hans Dockter
Gradle Project lead
http://www.gradle.org
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
