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.
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'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?
I don't particularly like the name 'master' either - this implies to me that
there is some type of master/slave relationship. This is just the configuration
that holds the primary archive. Perhaps 'main' or 'archive' would be better.
I think I like just 'archive', then 'buildArchive' would be equivalent to the
current 'libs' task.
--
Steve Appling
Automated Logic Research Team
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
