Well I can't speak for Google as a whole :) but speaking for myself (and I think the other GWT engineers), we want people to easily use GWT in every conceivable way. We've tried to balance providing some useful tools (like Eclipse and Ant file generation) with being tool agnostic. We want you to use whatever tools you like best, and have the power to integrate with other tools as you see fit. The compiler and shell scripts are a way of saying, "Here's the bare minimum you need to get this to run; extrapolate from here to fit your own build environment." We don't want to force you to use a particular technology.
Last few days I've spent on developing AJAX Developer Suite - suite which integrates GWT, Maven 2 and Jetty 6. With it you can create real-time AJAX applications. To create your own project you can simply use Maven blank project (in the future it will have a goal to run Google browser). Currently project is on planning stage. Any help appreciated.
Thanks for taking the time to respond to my question and thanks for the pointer, much appreciated.
Being so actively in present in this group really gives everbody the feeling that you are 'bringing' this cool technology to the community, instead of just throwing it over the wall. Double thumbs up and keep up the good work...!
> Well I can't speak for Google as a whole :) but speaking for myself > (and I think the other GWT engineers), we want people to easily use GWT > in every conceivable way. We've tried to balance providing some useful > tools (like Eclipse and Ant file generation) with being tool agnostic. > We want you to use whatever tools you like best, and have the power to > integrate with other tools as you see fit. The compiler and shell > scripts are a way of saying, "Here's the bare minimum you need to get > this to run; extrapolate from here to fit your own build environment." > We don't want to force you to use a particular technology.
> By the way, Robert Cooper has a Maven plugin he talks about in this > article:
I've been working on a m2 plugin myself [1]. Very sloppy code and still needs lots of work, but I've managed to create a compile mojo. You can plug it into your pom.xml like this:
It assumes a different directory structure than the ones created by GWT's create script. The GWT stuff are to be put under ./src/main/gwt. The output goes to ./target/gwt/www.
Thank for putting your mojo code out there. I made a slight modification to pick up external source dependencies.
/** * Location of the source files. * * @parameter * @required */ private List sourceDirectories;
//added a loop to get all the source directories. private ClassLoader getClassLoader() throws MojoExecutionException { URLClassLoader myClassLoader = (URLClassLoader) getClass().getClassLoader();
URL[] originalUrls = myClassLoader.getURLs(); URL[] urls = new URL[originalUrls.length + sourceDirectories.size()]; for (int index = 0; index < originalUrls.length; ++index) { try { String url = originalUrls[index].toExternalForm(); urls[index] = new File(url.substring("file:".length())).toURI().toURL(); } catch (MalformedURLException e) { throw new MojoExecutionException("MalformedURLException", e); } }
shinobu wrote: > I've been working on a m2 plugin myself [1]. Very sloppy code and > still needs lots of work, but I've managed to create a compile mojo. > You can plug it into your pom.xml like this:
> It assumes a different directory structure than the ones created by > GWT's create script. The GWT stuff are to be put under ./src/main/gwt. > The output goes to ./target/gwt/www.