I understand your point of view,
I just want to notice Mojo project has been created to avoid such case
of multiple plugins for same use-cases / technology.
Anyone can get write acces to Mojo when donating a plugin, and this is
the primary place where maven user will search for maven a maven
plugin to support XX technology. It doesn't use the constraining
Apache fundation release and licensing rules, so Mojo committer are
free to create and promote nice plugins.
I was not aware of googlecode gwt-maven plugin when I searched one,
and found the one in Mojo sandbox that required some improvements. I
later was pointed to google code, but hopefully I didn't plan same
features.
Same issue may occur with android or any other technology. I myself
planned to study android and to support it as part of Mojo, but your
comment let me thing there is allready plugins available *somewhere*
for that ;) It would be better for such project to support own
plugins, to avoid such ambiguous brother plugins.
We (Mojo project) could also add links to such 3rd party plugins.
Cheers,
Nicolas
On 23 nov, 08:25, "Ray Cromwell" <
cromwell...@gmail.com> wrote:
> Nicolas,
> I hope you didn't take my comment the wrong way. I just wanted to
> point out that Charlie Collin's plugin has been out a lot longer and
> has many more people using it. It's great that the Mojo version has
> finally been brought up to a similar state, I just lament the fact
> that there are so few people maintaining gwt maven plugins that it
> might serve better to have a unified project. Charlie Collins recently
> did this with his Android Maven pluging, merging it with the Masa
> plugin which had a different featureset.
>
> I am not involved in either project, I'm just a heavy user of
> gwt-maven plugin from Charlie's project, and long term, I'd like to
> see a sort of defacto standard GWT maven plugin, defacto standard GWT
> repo, etc. Right now, everyone and their brother is putting GWT
> packages into repos, using various packaging schemes.
>
> -Ray
>
> On Sat, Nov 22, 2008 at 11:18 PM, nicolas.deloof
>