On Monday 29 March 2010 07:07:27, Adam Murdoch wrote:
> ... For example, we might do something like:
>
> artifacts {
> dists { // define a new artifact publication
> contains binZip, allZip, srcZip // add in the archives
> publishTo webdavRepository(...) // define where it is published to
> }
> }
>
> This might automatically add a publishDists task which does the work of
> publishing the distributions. Or not. We might make it explicit:
>
> artifacts {
> dists {
> contains binZip, allZip, srcZip
> }
> }
>
> task uploadDists(type: Upload) {
> from artifacts.dists
> to webdavRepository(...)
> }
Very great plans! I already love it.
Putting the definition of a repository access to configuration section is more
natural / native than putting it to a task.
Your sample is great - the uploadDists-task is only needed to trigger the
upload but the definition stays at configuration section. Yes, I like it :)
kind regards
Geronimo
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
