Hi,
you have to the groovy dependency to your dependency definition. the following lines of code loads groovy 1.7.2 to your classpath from the central maven repo:

repositories {
    mavenCentral()
}

dependencies {
    groovy "org.codehaus.groovy:1.7.2"
}

regards,
René


Am 14.06.10 18:57, schrieb boardtc:
I added.
apply plugin: 'groovy'
to the build file and added all the .directories below, including the corresponding ones for groovy.

The groovy jars were not added to the .classpath though....

Tom.



    On 14 June 2010 17:09, Jason Porter <lightguard.jp
    <http://lightguard.jp>@gmail.com <http://gmail.com>> wrote:

        I'm guessing it's because you don't have any files in your
        test project.

        For a java project the default layout Gradle is expecting is

        src/main/java
        src/test/java
        src/main/resources
        src/test/resources

        The eclipse generation may not be putting anything in there
        because
        you don't have those directories, nor any files in them.

        On Mon, Jun 14, 2010 at 09:58, boardtc <boar...@gmail.com
        <mailto:boar...@gmail.com>> wrote:
        > Thanks Jason. That worked.
        >
        http://www.gradle.org/latest/docs/userguide/eclipse_plugin.html said
        if used
        > together with the Java plugin but I did not know it meant
        that line needed
        > to be added to the build file.
        > I'm not sure what I have now though? Like Maven, I expected
        some kind of
        > src\main\resources\test structure but all I see is a
        .project file and
        > a classpath....
        > <projectDescription>
        > <name>Tester</name>
        > <comment/>
        > <projects/>
        > <natures>
        > <nature>org.eclipse.jdt.core.javanature</nature>
        > </natures>
        > <buildSpec>
        > <buildCommand>
        > <name>org.eclipse.jdt.core.javabuilder</name>
        > <arguments/>
        > </buildCommand>
        > </buildSpec>
        > </projectDescription>
        > <classpath>
        > <classpathentry kind="output" path="build/classes/main"/>
        > <classpathentry kind="con"
        > path="org.eclipse.jdt.launching.JRE_CONTAINER"/>
        > </classpath>
        > Cheers,
        >
        > Tom.
        >
        >
        > On 14 June 2010 14:40, Jason Porter <lightguard.jp
        <http://lightguard.jp>@gmail.com <http://gmail.com>> wrote:
        >>
        >> Add apply plugin: 'java' either above or below your first
        apply line
        >> then you'll see tasks, and you can create an eclipse
        project with
        >> "gradle eclipse".  Without specifying a project type (java,
        groovy,
        >> scala, war, osgi, etc) gradle doesn't know what you want to
        do.  It's
        >> not like maven where it assumes you're going to be building
        a java
        >> project by default.
        >>
        >> On Mon, Jun 14, 2010 at 07:01, boardtc <boar...@gmail.com
        <mailto:boar...@gmail.com>> wrote:
        >> > Hi John,
        >> > Thanks for your mail. Yes, I am running gradle in the
        directory which
        >> > contains the file build.gradle (which has just the one line)
        >> >
        >> > Cheers,
        >> >
        >> > Tom.
        >> >
        >> >
        >> > On 14 June 2010 13:45, John Murph <jmurph....@gmail.com
        <mailto:jmurph....@gmail.com>> wrote:
        >> >>
        >> >> Some silly questions, but just in case:
        >> >>
        >> >> Are you running Gradle from the directory that contains
        your build
        >> >> file?
        >> >> Is the build file called "build.gradle"?
        >> >>
        >> >> There are command line options to allow these
        constraints to be
        >> >> avoided,
        >> >> but I wouldn't use those options until after I had it
        working.
        >> >>
        >> >> --
        >> >> John Murph
        >> >> Automated Logic Research Team
        >> >
        >> >
        >>
        >>
        >>
        >> --
        >> Jason Porter
        >> http://lightguard-jp.blogspot.com
        >> http://twitter.com/lightguardjp
        >>
        >> Software Engineer
        >> Open Source Advocate
        >>
        >> PGP key id: 926CCFF5
        >> PGP key available at: keyserver.net <http://keyserver.net>,
        pgp.mit.edu <http://pgp.mit.edu>
        >>
        >>
        ---------------------------------------------------------------------
        >> To unsubscribe from this list, please visit:
        >>
        >> http://xircles.codehaus.org/manage_email
        >>
        >>
        >
        >



        --
        Jason Porter
        http://lightguard-jp.blogspot.com
        http://twitter.com/lightguardjp

        Software Engineer
        Open Source Advocate

        PGP key id: 926CCFF5
        PGP key available at: keyserver.net <http://keyserver.net>,
        pgp.mit.edu <http://pgp.mit.edu>

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

        http://xircles.codehaus.org/manage_email






--
------------------------------------
Rene Groeschke

r...@breskeby.com
http://www.breskeby.com
http://twitter.com/breskeby
------------------------------------

Reply via email to