On Fri, 12 Nov 2004 11:49:25 +0100, Stefan Bodewig <[EMAIL PROTECTED]> wrote: > On Thu, 11 Nov 2004, Steve Loughran <[EMAIL PROTECTED]> wrote: > > > I want the opinon of other developers on this topic. > > Let me admit that you've lost me (in particular since I have rather > limited bandwidth ATM - where M seems to be months rather than > moment). > > Is there any place I can read up on your different concepts without > reading sources?
A bit earlier in the thread, I tried to summarize them: 1. The "getLibraries" task. Fetches a set of libraries to be fetched from a repository and copied (optionally renaming them) into a designated directory. Uses semantics analogous to "copy" to decide whether the libraries already present need to be replaced. The repository for a set of libraries is not inherently part of the task, and may be specified either within the task or on the command line. Optionally defines a classpath from the fetched libraries. 2. The "dependencies" task. Identifies a set of files in a repository by version and creates either a classpath or a fileset (or both) based on the definition. Maintains a local cache of the files which may be shared by multiple projects, loading it from the specified repository. Cached filenames include version information. The repository is an inherent part of the definition. May conditionally exclude entries from the set. The first is essentially a generalized "copy" task while the second is a generalized "fileset" or "path" task. You can also read the documentation for the latest version of the dependencies task at <http://www.httpunit.org/doc/dependencies.html> --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
