Hi all,

I am looking to migrate half of a build process to Gradle, and am
wondering about what kind of automation I can apply to the checking
out of code.

That is; The examples I find regarding Gradle, deal with the very easy
building of code, using conventions, cutting down the amount of code
necessary.
But is there a way to declare the source of the code (i.e., a
subversion repository) and get it to build automatically from there?
Or does this part have to be completely custom, with my using
subversion from the exec command (as the helpful people at Gradle have
shown me how to do already).

To be more specific, here is my situation;

We build

1) the main product, and
2) a set of plugins which depend on an API which is part of that product.

It is the build of the plugins which I wish to build with Gradle (too
much work to migrate the whole lot at the moment).

So, at the moment, Ant checks out the source for the main product, and
builds it. Sources are at a known (by property) directory, and the jar
files built to another property.

What we need to do is now build the plugins against the main product.

However, we build (depending on configuration) not the whole source
tree. In subversion we have the usual

product_name/trunk
                    /tags/1.21.1
                           /1.21.2
                    /branches

and when we build, we choose to build one of these branches (trunk, or
tags/1.21.1/ or tags/1.21.2, or... etc)

So, similarly, when we build the trunk of the main product, we want to
build the trunk of all the available plugins, found at

plugins/plugin_name/trunk|tags|branches

Do I need to build this up myself, in the way I would anyway using
Ant,  (checkout myself, creating folders, programmatically selecting
branch etc)
or is there some mechanism that means gradle can do all this for me
(maybe I have to modify my repository structure or something? )
>From how this sounds, what non-typical kinds of problems can anyone
imagine I might come across in this task of mine?
Or is just a matter of reading further into the doco, and learning how
things are done in Gradle, and I will see the light?

Thanks for any advice,

Sean

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

    http://xircles.codehaus.org/manage_email


Reply via email to