[
http://jira.codehaus.org/browse/MOJO-549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_91536
]
Jörg Hohwiller commented on MOJO-549:
-------------------------------------
To put my two cents in:
It really seems to make no sense to have 4 different plugins for the same
thing.
The plugin in the mojo sandbox seems pretty dead: it requires the resources to
be in src/main/java (what is odd) and does not support including other gwt
modules or running the gwt app.
I would l appreciate if the plugin attached to this issue would go to sandbox
and replace the dead one.
The approach of the plugin at googlecode (its actually in group-id
'com.totsp.gwt' and not 'com.google.gwt') requires an external gwt installation
what makes in inacceptable from my point of view. I talked to the developer
about this but he is not willing to change this.
I like your idea of using the gwt.version and flavor for the dependency.
Anyways I would suggest that gwt artifacts should go to ibiblio and there
should also be a general gwt-dev-VERSION.pom that does the OS choice according
to the flavor.
FYI: your site.xml is broken the banner tags have to go outside the body tag.
> 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
