Hi Peter,
On May 1, 2008, at 8:32 AM, Hans Dockter wrote:
On Apr 30, 2008, at 7:06 PM, Peter Niederwieser wrote:
hdockter wrote:
If this build were successful, you could download the Gradle with
Groovy 1.6 distribution from teamcity.
This would be good enough for me as an interim solution.
hdockter wrote:
There might be another possibility for just using the groovyc 1.6 by
creating a new taskdef for groovyc with the 1.6 classpath. I don't
know if this is possible when Groovy 1.5.5 is also in the Ant
classpath.
If Gradle wants to become an attractive and reliable choice for
building
Groovy projects (and I'm sure it does!), it's really important
that it
completely separates the Groovy distribution used internally from
the Groovy
distribution used to build a project. In my opinion there
shouldn't even be
an option to build using the internal distribution - such a
coupling is just
too evil.
I agree. In fact this is the case right now except for the
compiler. I just haven't thought about it properly. As Russel
pointed out in the other thread, what I'm interested in is code
that gives evidence whether it is compiled with groovy 1.6 or not,
because of possible classpath issues.
What I'm asking here is if you can provide such code ;). Or by what
other means can one recognizes which groovyc is used? I'm want to
release 0.1.4 within the next days and I would like to include this
feature.
- Hans
I want to add a default groovy configuration to the dependencies of
a Groovy project.
Users can add to it the groovy jars with all the libraries they
need. This configuration is extended by the compile configuration.
The groovy configuration will be also used for getting the groovyc.
I'm wondering if there should be a convenience behavior, which
detects GROOVY_HOME and uses the jars from there if nothing else is
specified.
- Hans
Cheers,
Peter
--
View this message in context: http://www.nabble.com/Building-
Groovy-projects-with-Gradle-tp16926886p16987383.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
