Thanks, I'll try to include some sample project links on github to demonstrate what I have problems with.
Thanks, James On Fri, May 20, 2011 at 12:27 PM, Kris De Volder <[email protected]> wrote: > Hi Roger, James, > > Some of the things you both mentioned: > - trouble with the menus being greyed > - problems with single module projects > > Sound like they are bugs that should be fixed. I would encourage you to > raise a bug issue about those problems, especially if they are reproducible. > > If you don't think this stuff ready for "prime time" yet, you may be right. > This is our first public release of the tools and it hasn't really > been tested "out in the real world". If you want to help, the best thing to do > is raise bug tracker issues for the problems you experience. > > See this link on where to report bugs: > http://static.springsource.org/sts/docs/2.7.0.M1/reference/html/gradle/faq.html#a18 > > I'm really grateful that you guys took the time and energy to try this out... > Now I'm hoping you'll put a bit more effort and file some really > great bug tracker issues about your troubles :-) > > On some other topic Roger mentioned: > >> > So my project View is: >> > >> > JRE System Library >> > GWT SDK 2.2 >> > Gradle Dependencies >> > Referenced Libraries. >> > >> > if I try to run the gradle build, it never (ever) makes use >> > of/see's any of >> > the jars in the GWT SDK 2.2 >> > >> > So it appears the execution classpath for gradle in this case, >> > isn't being >> > superset'd by what eclipse knows about > > Right, that is really to be expected if you added those entries to > the classpath in Eclipse there's really nothing in your build script > telling it that it should be using those added jars... so it won't. > > That's not a bug (unless I completely misunderstood what you were > trying to do). > > The way the tooling works is that it tries, as much as possible, to > configure an Eclipse project based on what your build script says, > not the other way around. > > Now... you could make a case that the other way around should also > work. But this is quite tricky, and the current version of the > Gradle tooling API doesn't provide methods for the IDE to > contribute dependencies to the build. > > Still this could be a feature request... if you care to raise it > on the Jira tracker (same place where you'd file bugs). > > Kris > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > > --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
