On Nov 6, 2008, at 8:27 AM, mvlcek wrote:
If I deliver a new version of a project,
- I have to determine the delivery directory name (something with
project
group, name and date)
- create the directory
- create a source zip and copy it to the directory
- copy (some of) the jars/wars created in the libs task to the
directory
- copy other files like release notes to the directory
- (there should be no ivy.xml(s) in the delivery directory)
Is this something I can do with the dists task (how?) or should I
rather
create a custom task?
The dists task has two purposes. Functionality wise it is the same as
the libs task. It is solely for creating archives. Usually
distribution archives, but this is up to you. The other purpose it to
provide a lifecycle hook for doing custom stuff when building dists.
The uploadDists task uploads the archives defined in the dists task.
In contrast to uploadLibs, no ivy.xml is deployed.
We might think about how Gradle can provide in the future out-of-the-
box functionality for generating a distribution . Like automatically
copying the sources, having a top level folder that gets
automatically copied (for release notes, licenses, ...) and other
stuff. Right now who have to do this manually.
- Hans
--
Hans Dockter
Gradle Project lead
http://www.gradle.org
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
