Thanks for your patience Jason. Cool gradle uses the same structure as Maven. I thought it would build the skeleton structure like maven does, but one needs to create it by hand
I have a couple of groovy files in the project. I tried it with a java file but it still did not build a skeleton. I googled around but I am not sure what I need to add to the build.gradle to add groovy to the eclipse .classpath? Cheers, Tom. On 14 June 2010 17:09, Jason Porter <[email protected]> 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 <[email protected]> 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 <[email protected]> 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 <[email protected]> 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 <[email protected]> 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, 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, pgp.mit.edu > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > >
