Yah, its a pitty, but the Google guys are pretty down on Maven.
I once asked them to look into making it more maven friendly, and got
throughly blasted.
if I remember correctly the comment from one of the GWT developers was
something along the lines of "we don't want to waste our time with
garbage like maven".
I didn't bother to argue about it, because if you know maven and like
it, you know why its advantageous, and if your that set against it it
won't matter what others say.
However there are a few maven plugins for it, and combined with the
war overlay feature, it not to hard to get it all working and
integrate with other projects.
- Brill Pappin
On 8-Apr-09, at 10:46 AM, Casper Bang wrote:
Peter Thomas did a great side by side you should checkout:
Good article, if perhaps a bit one-sided. I can understand how
separation-of-concerns/composability comes slightly more natural to
Wicket.
However the performance, flexibility and component repertoire of GWT
along
with steadily more capable browsers leaves me with a feeling that
"I'll get
more bang for my buck".
Until GWT has a build system that is better I'll stay away from it.
Since version 1.6 today, it uses normal Ant scripts (which I suppose
is easy
to mavenize).
Thanks guys,
/Casper
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
