Comments on: GWT 2.0 RC1 is out! http://blog.gerardin.info/archives/565 Java, Agile, the Web and other nice things Sun, 15 Jan 2012 01:56:06 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: olivier http://blog.gerardin.info/archives/565/comment-page-1#comment-805 olivier Fri, 20 Nov 2009 09:01:53 +0000 http://blog.gerardin.info/?p=565#comment-805 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 :) 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 :)

]]> By: Alexander Orlov http://blog.gerardin.info/archives/565/comment-page-1#comment-803 Alexander Orlov Fri, 20 Nov 2009 00:04:50 +0000 http://blog.gerardin.info/?p=565#comment-803 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. 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.

]]> By: olivier http://blog.gerardin.info/archives/565/comment-page-1#comment-801 olivier Thu, 19 Nov 2009 23:44:55 +0000 http://blog.gerardin.info/?p=565#comment-801 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. 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.

]]> By: Alexander Orlov http://blog.gerardin.info/archives/565/comment-page-1#comment-800 Alexander Orlov Thu, 19 Nov 2009 23:30:34 +0000 http://blog.gerardin.info/?p=565#comment-800 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. 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.

]]> By: olivier http://blog.gerardin.info/archives/565/comment-page-1#comment-798 olivier Wed, 18 Nov 2009 21:35:33 +0000 http://blog.gerardin.info/?p=565#comment-798 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. 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.

]]> By: Alexander Orlov http://blog.gerardin.info/archives/565/comment-page-1#comment-797 Alexander Orlov Wed, 18 Nov 2009 19:43:26 +0000 http://blog.gerardin.info/?p=565#comment-797 I would recommend to use just Ant instead of the *$%#$(8 Eclipse plugin. I would recommend to use just Ant instead of the *$%#$(8 Eclipse plugin.

]]>