On Wed, Dec 23, 2009 at 4:15 AM, Tim Taylor <[email protected]> wrote:
> At work I manage a build consisting of Java and Perl projects. The current > build is a mixture of GNU make and Ant. I've been experimenting with Gradle > (0.8). Naturally Gradle is well suited to managing the Java parts of the > build. Less so for managing the Perl parts. Specifically Perl external > module dependencies (e.g. CPAN modules) are a challenge. > > Perl CPAN modules are distributed as source. The CPAN system includes > dependency metadata. Perl includes the `cpan` command which works similar to > apt or yum, except that instead of downloading binary distributions, cpan > manages the downloading of source dependencies, building and installing them > into your Perl tree. > > For reasons important to us we don't rely on the `cpan` tool. Instead we > recreate its functionality in our Makefile. Evaluating Gradle as a way to > consolidate on one build system, I'm find that the only way to support > source dependencies is a large amount of scripting. > > Are there plans to (or interest in) support external dependencies that are > only available in source code form? > We think this is a great feature. In fact project dependencies fall already into this category. You need to build them before they are available and this is reflected in our model (e.g. there is the Buildable interface). We think it would be very cool to have all different kinds of buildable dependencies (e.g. GitProject/SvnProject/...) provided by Grale. You could already hook in your own types of buildable dependencies into Gradle configurations. - Hans -- Hans Dockter Gradle Project Manager http://www.gradle.org > Cheers, > Tim > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > >
