Hi Allan,
On May 6, 2008, at 4:03 AM, Allan Lewis wrote:
Hans,
I downloaded the 0.1.4 release and tried your example, but get the
following. Thoughts?
Build aborted anormally. Run with -s option to get stacktrace. Run
with -d option to get all debug info including stack
trace. Run (additionally) with -f option to get the full (very
verbose) stacktrace
Exception: org.gradle.api.GradleScriptException:
java.lang.ClassNotFoundException: groovy.lang.GroovyShell
Buildscript=g
radlefile No line info available from stacktrace.
This is a bug. It works on my Mac but not on Windows (and probably
not on Linux). I have to check when I have time.
Sorry for this
- Hans
From: Hans Dockter [mailto:[EMAIL PROTECTED]
Sent: Monday, May 05, 2008 7:05 PM
To: [email protected]
Subject: Re: [gradle-user] Advice on multi-project/build source setup
Hi Allan,
with the new 0.1.4 release a couple of things have changed.
I have attached a modified example zip for your use case.
- Hans
On May 2, 2008, at 1:58 PM, Allan Lewis wrote:
Hans,
This is great, thanks! I need to play with things a bit more to get
things
fully functional in my real-world case, but what you laid out
definitely
works. Would be great if doing things like this could become a
little more
seamless and tied into the build to reduce some of the boilerplate
stuff (as
you mentioned earlier).
Allan
--
View this message in context: http://www.nabble.com/Advice-on-multi-
project-build-source-setup-tp16960881p17016785.html
Sent from the gradle-user mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
--
Hans Dockter
Gradle Project lead
http://www.gradle.org
--
Hans Dockter
Gradle Project lead
http://www.gradle.org
