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 On Thu, May 19, 2011 at 8:10 PM, Roger Studner <[email protected]> wrote: > Or, I guess let me be more specific with what i'm seeing (sorry, last email > sounded like a rant) > > I have a tiny GWT project, that I want to work on in STS.. and use gradle > for most (but not all) of the build/launch process (so, i'm not using the > community gwt-gradle plugin yet etc). > > One thing i'm noticing, is that if I have *any jars* in the workspace OTHER > than the ones that are defined in build.gradle.. then the run as Gradle > stuff never see's them. > > Example: > > I have 100% of all my jars (spring, mockito etc) in build.gradle.. BUT, > because this is STS/Google tooling.. I have a GWT SDK defined and it is > using that. > > 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 > > Best, > Roger > > > --------------------------------------------------------------------- > 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
