« Return to Thread: About generating artifacts in 0.6

Re: About generating artifacts in 0.6

by Tom Eyckmans :: Rate this Message:

Reply to Author | View in Thread



2009/4/17 Hans Dockter <mail@...>
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.

What is new in 0.6 is, that the Java plugin adds also the rule, that a taskname with the pattern build<configurationName> (can you think of a better name?) generates the artifacts associated with the configuration.
(btw I like this a lot :)), I don't have a problem with build but a possible alternative could be make ?

BTW: I'm not that happy with the configuration name 'master'. I have taken it from the recommended ivy setup of the 'Ant in Action' book. I don't have a good alternative. Any more specific name (e.g. libs) might be misleading for certain scenarios. Thought?
base ? from base dependencies (which are the miminal dependencies so base from basic)


- Hans

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





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

  http://xircles.codehaus.org/manage_email



 « Return to Thread: About generating artifacts in 0.6