Hi, I'm sorry that I forgot the details.
What I wanted to do and my expectations about it: I cloned the gradle repo and wanted to create the eclipse project files. Therefore I changed into the top level directory of the repository and executed 'gradle eclipse'. My expectation was, that all the required eclipse files will be generated and I can open the gradle project in Eclipse for further inspection. Probably my expectation was wrong here. Thanks, Ingo -- San Francisco Blog <http://8880km.blogspot.com> "today is tomorrows past blog" <http://ingorichter.blogspot.com> LinkedIn Profile: <http://www.linkedin.com/in/ingorichter> twitter: <http://twitter.com/ingorichter> On Tue, Aug 9, 2011 at 2:20 PM, Szczepan Faber <[email protected]> wrote: > >Is this a bug? > > I don't know - you need to be a tiny bit more specific :) > > I suggest to submit a jira ticket with the information of your build script > and the expected/actual results of gradle eclipse and we will take a look at > it. > > Cheers! > > On Tue, Aug 9, 2011 at 10:47 PM, Ingo Richter <[email protected]>wrote: > >> Hi, >> >> I tried 'gradlew eclipse' several times in the last weeks, but it doesn't >> work for me. The generated .classpath and .project files seem to miss a lot >> of information to be recognized by Eclipse. For example, the source folder >> is missing. >> I tried 'gradlew idea' and this seems to work much better. >> >> Is this a bug? >> >> Thanks, >> Ingo >> -- >> San Francisco Blog <http://8880km.blogspot.com> >> "today is tomorrows past blog" <http://ingorichter.blogspot.com> >> LinkedIn Profile: <http://www.linkedin.com/in/ingorichter> >> twitter: <http://twitter.com/ingorichter> >> >> > > > -- > Szczepan Faber > Principal engineer@gradleware > Lead@mockito >
