Re: [gradle-user] Re: [ANN} Gradle Eclipse Plugin

[Roger Studner]

Yeah Kris -- it makes sense that it wouldn't work (picking up the other configured jars). I guess the trick (as mentioned in the plugin docs).. is how this works when mixed with other project "natures".. since the GWT one of course wants to put its own GWT into the project to work.. at some point, you'd end up (in one place or another) either having 2 copies of everything, or 0. But a great first effort.. i'll keep hammering on it to try to find at least workable use cases Roger Kris De Volder May 20, 2011 1:27 PM 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 :-) 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 James Carr May 19, 2011 10:12 PM Hi Roger, I got this working at work today and here's a few things I've discovered. For starters, you'll need to be using a multi-module project as I always seem to get an exception when using a single module project setup. Also, after my full day of using it I'll have to say it is a great step in the right direction but far from ready for primetime yet. For now using the "external tool" option to call gradle eclipse is good enough for us. :) I'll continue using it through nightly installs though. I am confident it will wind up great and plan to report any JIRA issues I have. Thanks, James --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email