try {} catch ()

Java, Agile, the Web and other nice things

Nov

18

GWT 2.0 RC1 is out!

By Olivier Gérardin

Logo GWTBruce Johnson:

Hi folks!
GWT 2.0 RC1 is now ready for you to try. The full documentation is still very much a work in progress, but you can at least start trying out the GWT SDK distribution and the Google Plugin for Eclipse using the following
instructions:
http://code.google.com/p/google-web-toolkit/wiki/GWT_2_0_RC
GWT 2.0 is going to be a big release, so don’t be surprised if there are a few bumps and surprises as we continue to finalize everything.

Read full announcement on GWT group


6 Responses so far

I would recommend to use just Ant instead of the *$%#$(8 Eclipse plugin.

Could you elaborate? I’ve been quite happy with the Eclipse plugin, what’s wrong with it?
Besides, ant and the plugin serve different purposes, ant is designed for build automation not IDE integration.

Never claimed that Ant were designed for IDEs. However you can use Ant out of any IDE (I prefer IntelliJ IDEA). It’s just with Ant you have more control about the building process. You can supply more parameters and a UI thingy which an Eclipse plugin is, may change its interface, crash or do things you don’t want to be done (bugs!). Ant is just reliable, fast and keeps its “interface”.

And one of the main advantages: With Ant you aren’t bound to a specific IDE and especially Eclipse… Oh my god, how do I hate this IDE… It’s the second worst thing after Win95.

You said it, ant is for the building process. The plugin is for creating GWT projects, modules, host pages, run configurations etc. Sorry but I still don’t see how they compete with each other.

Because they don’t.

But you can also create GWT projects, modules, unit tests and I18n files using the supplied command line tools. No, it has nothing to do with Ant at all… but you can create GWT projects etc. also from the same command line where you are calling your Ant targets. The plugin does not support unit test and/or I18n creation? So you have still to go to the command line…

The POINT IS: Why using additional tools if you can do the same things faster and with more customization options with already existing tools? Furthermore you’ll understand GWT better if you are using Ant instead of the plugin. The plugin may crash (and believe me it will!) but Ant is a well tested and reliable tool.

Why? because when I work in the IDE, I want to be able to do everything I need to do without leaving the IDE. Plus, there are things only a plugin can do, such as specific refactorings and checks (for example, keeping the base interface and async version in sync).
But everyone works as they like to :)

Leave a comment