[
http://jira.codehaus.org/browse/MOJO-549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_91037
]
Anagnostopoulos Kostis commented on MOJO-549:
---------------------------------------------
Hi Brill,
(i hope this posting is not too late to take notice of...)
Just by scanning through the src code of both plugins, i notice that the
google-code's m2 plugin invokes the GWT compiler using a command line, spwaning
a new os process!
Not a very elegant way...
I'm using the codehaus's gwt plugin and i find it stable enough for an alpha
release and i preffer it implmenetation since it invokes
com.google.gwt.dev.GWTCompiler directly.
Also, from a functionality standpoint, i see that the google's plugin tries to
implement a pass-par-tout that ends up re-inventing the wheel (i.e. attaching
sources, packaging war, multi-module in a single maven module), so i preffer
Kristian's simpler approach.
Therefore, i would be glad to help porting Kristian's plugin into mojo as a
first class citizen.
Anyone else interested in contributing?
(Eric Redmond?)
Finally, i think we should start using this jira issue for any subsequent
conversations:
http://jira.codehaus.org/browse/MOJO-549
Regards,
Kostis
On 3/15/07, Brill Pappin <[EMAIL PROTECTED]> wrote:
> I've now tried out both...
> the google one actually works a bit better so far and they did manage
> to come up with something pretty good once you actually get it to
> work... it still need a lot of work to be a mainstream plugin (missing
> some key features).
>
> I do think the google folks could use some input from the maven guru's
> at Codehaus as they do things a bit "funny". Not sure I can pin one
> thing down off the top of my head, but I got the "unfinished" feeling
> when using it that I usually don't get from codehaus plugins (even the
> sandbox plugins).
>
> Frankly I think that what this is really going to take, is a rewrite
> of Google's tool wrapper (which should be able to happen without
> causing to much in the way of upgrade headaches) to make it more
> configurable.
>
> - Brill Pappin
> submitting new gwt-plugin
> -------------------------
>
> Key: MOJO-549
> URL: http://jira.codehaus.org/browse/MOJO-549
> Project: Mojo
> Issue Type: New Feature
> Components: Plugin Submission
> Environment: Gentoo Linux, maven-2.0.4, java build Blackdown-1.4.2-03
> Reporter: kristian meier
> Attachments: gwt-plugin.tar.gz, gwt-plugin2.tar.gz
>
>
> after asking the mojo-mailing list if there is interest in a
> gwt-maven-plugin, I hereby attaching the plugin code. I tried to obey the
> developer guidelines, but I have to admint I did have quite a struggle with
> it. so any feedback is welcome.
> I wanted to contribute a plugin with which you can compile GWT applications
> (code.google.com/gwt) from within maven. actually I have also two archetypes
> along with this plugin, but I do not know how to incorporate these in the
> given plugin structure of codehaus. so I just took the plugin tried to follow
> the guidelines as much as possible and added some documentation to it.
> the best understanding you get if you follow the example from the docu. I
> also stopped at a certain point, because first I want to see what Codehaus is
> doing with this and how I can contribute to this plugin when it is part of
> the mojo-project.
> with best wishes
> Kristian
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
