0.9 release

69 views
Skip to first unread message

David Dawson

unread,
Jun 18, 2013, 8:24:49 AM6/18/13
to grail...@googlegroups.com
Hi guys,

I've released the 0.9 version of the GWT plugin.


I've focused mainly on stabilisation, bug fixing and improving the dev experience for this release.

I'd appreciate some testing of the changes and regression checks against your apps.

Next release will focus on improvements, if you have any suggestions for what to prioritise, please throw them in now.  Issues with pull requests will, of course, be prioritised.

Best,

David.

--

David Dawson -  Simplicity Itself,  Founder and Principal Consultant


Web: www.simplicityitself.com  

Skype   : davidadawson
Twitter : @davidthecoder

Nathan Dunn

unread,
Jun 18, 2013, 11:58:32 AM6/18/13
to grail...@googlegroups.com

I'm getting this error now that I updated to 0.9.  

Previously I had:

      compile(':gwt:0.8') {
          exclude 'spock'
      }

Nathan


Here is the BuildConfig.groovy:

        compile ':gwt:0.9'

% grails war 
| Compiling 250 source files.
| Error Compilation error: startup failed:
Compile error during compilation with javac.
/Users/NathanDunn/.grails/2.2.1/projects/metagenomicsdb/plugins/gwt-0.9/src/java/grails/plugins/gwt/client/GwtActionService.java:3: package com.google.gwt.user.client.rpc does not exist
import com.google.gwt.user.client.rpc.RemoteService;
                                     ^
/Users/NathanDunn/.grails/2.2.1/projects/metagenomicsdb/plugins/gwt-0.9/src/java/grails/plugins/gwt/client/GwtActionService.java:12: cannot find symbol
symbol: class RemoteService
public interface GwtActionService extends RemoteService {
                                          ^
/Users/NathanDunn/.grails/2.2.1/projects/metagenomicsdb/plugins/gwt-0.9/src/java/grails/plugins/gwt/client/GwtActionServiceAsync.java:3: package com.google.gwt.user.client.rpc does not exist
import com.google.gwt.user.client.rpc.AsyncCallback;
                                     ^
/Users/NathanDunn/.grails/2.2.1/projects/metagenomicsdb/plugins/gwt-0.9/src/java/grails/plugins/gwt/client/GwtActionServiceAsync.java:11: cannot find symbol
symbol  : class AsyncCallback
location: interface grails.plugins.gwt.client.GwtActionServiceAsync
    <T extends Response> void execute(Action<T> action, AsyncCallback<T> callback);
                                                        ^
Note: /Users/NathanDunn/.grails/2.2.1/projects/metagenomicsdb/plugins/shiro-1.1.4/src/java/org/apache/shiro/grails/LegacyShiroFilter.java uses or overrides a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
4 errors


1 error
NathanDunn:metagenomicsdb% 



--
 
---
You received this message because you are subscribed to the Google Groups "grails-gwt" group.
To unsubscribe from this group and stop receiving emails from it, send an email to grails-gwt+...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

Ben

unread,
Jun 18, 2013, 1:43:50 PM6/18/13
to grail...@googlegroups.com
Hi Nathan,

just to be sure, did you try to drop the Grails bomb and compile from scratch?

1) Delete the project folder under <user home>/.grails/2.2.1/projects/<your application>
2) Run a 'grails clean'
3) Run a 'grails compile', run in 2-3 times if it doesn't succeed at once

Cheers,
Ben


2013/6/18 Nathan Dunn <nd...@cas.uoregon.edu>

Nathan Dunn

unread,
Jun 18, 2013, 3:45:34 PM6/18/13
to grail...@googlegroups.com

I did exactly that (though I just wiped my ~/.grails directory).  Nothing has changed with my GWT (still works fine with the old GWT plugin) setup (2.5.1).  

Nathan

David Dawson

unread,
Jun 18, 2013, 3:48:27 PM6/18/13
to grail...@googlegroups.com

Which gwt version was the one you used before?  I'll check for a regression.

Nathan Dunn

unread,
Jun 18, 2013, 4:09:48 PM6/18/13
to grail...@googlegroups.com, grail...@googlegroups.com
Same 2.5.1 ... Only thing that changed was the plugin version. 

Nathan

Nathan Dunn

unread,
Jun 18, 2013, 5:55:55 PM6/18/13
to grail...@googlegroups.com

I get the same result if I create an empty grails project and add 

        compile ':gwt:0.9'

to the plugins section of BuildConfig.groovy
gwt-test.zip

Nathan Dunn

unread,
Jun 18, 2013, 7:28:43 PM6/18/13
to grail...@googlegroups.com
Wiped ~/.ivy2 and ~/.grails.   Doing a grails clean works fine if I revert back to 0.8, exclude "spock".  On 0.9 excluding "spock" doesn't work.   

On an empty project this works file (with compile) with 0.9.  Its possible it conflicts with another plugin.  


On Tuesday, June 18, 2013 1:09:48 PM UTC-7, Nathan Dunn wrote:

Nathan Dunn

unread,
Jun 19, 2013, 12:24:31 PM6/19/13
to grail...@googlegroups.com, david....@simplicityitself.com
The working path is:

rm -rf ~/.grails/2.2.1/projects/<project-path>

   compile(':gwt:0.8') {
          exclude 'spock'
      }

change that to 

   compile ':gwt:0.9'

It works.   

However, it fails when I do:
rm -rf ~/.grails/2.2.1/projects/<project-path>
compile ':gwt:0.9'

I then get the errors I got below.     I guess that I will post it in a bug . . . might be easier to track.  

David Dawson

unread,
Jun 20, 2013, 12:02:22 PM6/20/13
to grail...@googlegroups.com
Would you happen to be using an external GWT_HOME by any chance?

if so, could you try adding 

gwt {
version = "2.5.1"
}

into BuildConfig.groovy and rechecking?   It might be that the handling of GWT_HOME has been broken somehow (I'd be thrilled to remove it tbh, its a pest to maintain)

--
David Dawson

Dawson Systems Ltd

Email    : da...@dawsonsystems.com
Mobile : 07866011256
Jabber : da...@dawsonsystems.com
Skype   : davidadawson
Twitter : @davidthecoder

http://davidadawson.wordpress.com

Ben

unread,
Jun 20, 2013, 12:09:04 PM6/20/13
to grail...@googlegroups.com
Hi David,

I agree, it would be very nice to get rid of GWT_HOME. However, so far we never managed to get the gwt.version resolution mechanism to reliably work, there were always problem with the dependencies in the classpath or compilation errors at some point... so far I didn't manage to pinpoint the actual problem, though.

Does the gwt.verison mechanism is working for someone that has a more sophisticated application setup with multiple plugins that also contain GWT modules?

Cheers,
Ben


2013/6/20 David Dawson <david....@dawsonsystems.com>

--

David Dawson

unread,
Jun 20, 2013, 12:12:32 PM6/20/13
to grail...@googlegroups.com
Hi Ben,

I think you've mentioned this type of set up before (or I remember a bug)

The apps I maintain have GWT modules hosted in many plugins, however modules are built within each plugin and converted to javascript during plugin publishing. The top level application integrates the plugins into a single app, but does not GWT work of its own, its all just html and javascript by that point.

What does your layout look like?  I'd be interested to know how that could be handled better

Nathan Dunn

unread,
Jun 20, 2013, 1:35:44 PM6/20/13
to grail...@googlegroups.com

Yeah, I had been setting GWT_HOME as per the instructions:



I did over-ride the plugin (once installed) here:

~/.grails/2.2.1/projects/metagenomicsdb/plugins/gwt-0.9/dependencies.groovy

That works (I have to compile twice after a clean), but obviously a hack.  


So, here are the issues:
1 - Can I do this without GWT_HOME (and does it work better)?   If so, how?  I don't see any instructions on this?
2 - Doing an update on the plugin is a bit of a hack.  Is there a more programatic way I could specify this 

I looked here, it gives the options, but doesn't quite say where to put them:


I can't get it to work with the proper settings in Config.groovy or BuildConfig.groovy. 

I very much appreciate your help on this.  Thanks,

Nathan



Nathan Dunn

unread,
Jun 20, 2013, 2:06:24 PM6/20/13
to grail...@googlegroups.com

Sorry, I'm a bit dense. You meant at the bottom (or presumably at the top) of BuildConfig.groovy in its own block.  

gwt {
    version = "2.5.1"
}

I actually unset GWT_HOME, as well.   After a few tries (timeout errors during jar download?) it completed and compiled successfully.  So some quick comments:

1 - I think that this should be the preferred / default method in the instructions: http://grails.org/plugin/gwt
2 - I think that the version should be a required parameter, since it will be wrong about half of the time and cause errors. 
3 - I think that leaving the specification of GWT_HOME in there is good.  Occasionally, I've had to patch GWT and wanted to specify my own version.

Great plugin.   I'm not sure if you've seen this:


But in my experience, I would tend to agree (at least for the projects I've worked on).  

Nathan  


You received this message because you are subscribed to a topic in the Google Groups "grails-gwt" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/grails-gwt/nntvYXiGisg/unsubscribe.
To unsubscribe from this group and all its topics, send an email to grails-gwt+...@googlegroups.com.

David Dawson

unread,
Jun 23, 2013, 12:07:37 PM6/23/13
to grail...@googlegroups.com

Ok. It seems likely there has been a regression of the gwt_home handling in 0.9, I'll look into that tomorrow and hopefully confirm and issue a point release.

Nathan, would you mind putting those three points into jira? I think they are all very reasonable, having them in jira will let them be tracked and included in the next release.

Best

David

Nathan Dunn

unread,
Jun 23, 2013, 12:18:05 PM6/23/13
to grail...@googlegroups.com, grail...@googlegroups.com
Definitely. 

Nathan
Reply all
Reply to author
Forward
0 new messages