uses codehaus mojo plugin instead of gwt-maven

[Arthur Kalmenson]

Hi everyone,

I can't launch hosted mode in any of my projects because Maven is
picking up the Codehaus Mojo plugin instead. It fails because the new
plugin requires Maven 2.0.9, but this is very frustrating, I want it
to use the gwt-maven plugin. I haven't changed any settings in my POM
which worked perfectly fine on Friday. Here's the error:

arthur@ares:~/work/mshab/mshab-widgets$ mvn gwt:gwt
[INFO] Scanning for projects...
[INFO] Searching repository for plugin with prefix: 'gwt'.
[INFO] Ignoring available plugin update: 1.0 as it requires Maven version 2.0.9
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] The plugin 'org.codehaus.mojo:gwt-maven-plugin' does not exist
or no valid version could be found
[INFO] ------------------------------------------------------------------------
[INFO] For more information, run Maven with the -e switch
[INFO] ------------------------------------------------------------------------
[INFO] Total time: < 1 second
[INFO] Finished at: Mon Nov 24 11:20:50 EST 2008
[INFO] Final Memory: 1M/4M
[INFO] ------------------------------------------------------------------------

Thank you in advance.

Regards,
--
Arthur Kalmenson

[Arthur Kalmenson]

I should have posted the full scanning that Maven does when it hasn't
downloaded the Codehaus plugin:

arthur@ares:~/work/upma$ mvn gwt:gwt

[INFO] Scanning for projects...
[INFO] Searching repository for plugin with prefix: 'gwt'.

[INFO] artifact org.codehaus.mojo:gwt-maven-plugin: checking for
updates from gwt-maven-plugins
[INFO] artifact org.codehaus.mojo:gwt-maven-plugin: checking for
updates from central
Downloading: http://repo1.maven.org/maven2/org/codehaus/mojo/gwt-maven-plugin/1.0/gwt-maven-plugin-1.0.pom
7K downloaded

[INFO] Ignoring available plugin update: 1.0 as it requires Maven version 2.0.9
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] The plugin 'org.codehaus.mojo:gwt-maven-plugin' does not exist
or no valid version could be found
[INFO] ------------------------------------------------------------------------
[INFO] For more information, run Maven with the -e switch
[INFO] ------------------------------------------------------------------------

[INFO] Total time: 4 seconds
[INFO] Finished at: Mon Nov 24 11:45:07 EST 2008

[INFO] Final Memory: 1M/4M
[INFO] ------------------------------------------------------------------------

This is infuriating and very annoying :(

--
Arthur Kalmenson

[Mirko Nasato]

That's weird; only plugins from org.apache.maven should be picked up
automatically, not something from org.codehaus. What's in your
pom.xml?

2008/11/24 Arthur Kalmenson <arthu...@gmail.com>:

[Arthur Kalmenson]

Hi Mirko,

It seems to be a namespace conflict with the new Codehaus plugin. My
POM did not change between Friday (when it worked) and today (when it
stopped working). I'm guessing that Maven checks the Codehaus plugin
repository by default to see if it can handle the "gwt" goal, finds
that it can and downloads it.

quadmasta on the #gwt IRC channel suggested using "mvn
com.totsp.gwt:maven-googlewebtoolkit2-plugin:gwt" which works fine. Is
there a way to give the gwt-maven residence over codehaus?

P.S. I checked the global settings.xml and can't find codehaus there.

--
Arthur Kalmenson

[Mirko Nasato]

Hi Arthur,

Well it does say here that org.codehaus.mojo will be searched by default

http://maven.apache.org/guides/introduction/introduction-to-plugin-prefix-mapping.html

and it does seem that the other gwt-maven-plugin has been uploaded to
the central maven repository a couple of days ago

http://repo1.maven.org/maven2/org/codehaus/mojo/gwt-maven-plugin/1.0/

so what you say makes sense.

But if I type mvn gwt:gwt inside a project that doesn't declare any
gwt-maven plugin, what I get is

[INFO] Scanning for projects...
[INFO] Searching repository for plugin with prefix: 'gwt'.

[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------

[INFO] The plugin 'org.apache.maven.plugins:maven-gwt-plugin' does not

exist or no valid version could be found

and everything is working fine for me. So at this point the weird
thing is: why is it still working for me? Are other people having
problems?

Cheers

Mirko


2008/11/24 Arthur Kalmenson <arthu...@gmail.com>:

[Darren Hartford]

Just to confirm, my team has also run into this issue just recently today (11/24). This will definitely impact a large number of people.  I found the old issue from April talking about the codehaus plugin, and whether or not this project (google gwt-maven) was going to change their prefix or not. For those still stuck, resolution is to instead of 'mvn gwt:gwt', use: mvn com.totsp.gwt:maven-googlewebtoolkit2-plugin:gwt Reference link: http://code.google.com/p/gwt-maven/issues/detail?id=107 -D --- On Mon, 11/24/08, Mirko Nasato <mirko....@gmail.com> wrote:

[Charlie Collins]

The deal here is that 1.) Maven does check org.codehaus for plugins by
default, and 2.) the codehaus plugin was put in the CENTRAL repo on
the 22nd.

We need to change our prefix I guess, even it was suggested to the
Codehaus maintainer that he change his prefix several times, guess
that's not gonna happen (GWT-Maven is considerably older, and had the
name first).

So I can change the prefix easily, what should we change it to?

gwtmaven:

gwtm:

gwtmp:

mavengwt:

votes, or any other ideas?

On Nov 24, 4:59 pm, Darren Hartford <binarymon...@yahoo.com> wrote:
> Just to confirm, my team has also run into this issue just recently today (11/24).
>
> This will definitely impact a large number of people.  I found the old issue from April talking about the codehaus plugin, and whether or not this project (google gwt-maven) was going to change their prefix or not.
>
> For those still stuck, resolution is to instead of 'mvn gwt:gwt', use:
>
> mvn com.totsp.gwt:maven-googlewebtoolkit2-plugin:gwt
>
> Reference link:http://code.google.com/p/gwt-maven/issues/detail?id=107
>
> -D
>

> --- On Mon, 11/24/08, Mirko Nasato <mirko.nas...@gmail.com> wrote:
> From: Mirko Nasato <mirko.nas...@gmail.com>

> Subject: Re: uses codehaus mojo plugin instead of gwt-maven
> To: gwt-...@googlegroups.com
> Date: Monday, November 24, 2008, 12:58 PM
>
> Hi Arthur,
>
> Well it does say here that org.codehaus.mojo will be searched by default
>

> http://maven.apache.org/guides/introduction/introduction-to-plugin-pr...

>
> and it does seem that the other gwt-maven-plugin has been uploaded to
> the central maven repository a couple of days ago
>
>  http://repo1.maven.org/maven2/org/codehaus/mojo/gwt-maven-plugin/1.0/
>
> so what you say makes sense.
>
> But if I type mvn gwt:gwt inside a project that doesn't declare any
> gwt-maven plugin, what I get is
>
> [INFO] Scanning for projects...
> [INFO] Searching repository for plugin with prefix: 'gwt'.
> [INFO] ------------------------------------------------------------------------
> [ERROR] BUILD ERROR
> [INFO] ------------------------------------------------------------------------
> [INFO] The plugin 'org.apache.maven.plugins:maven-gwt-plugin' does not
> exist or no valid version could be found
>
> and everything is working fine for me. So at this point the weird
> thing is: why is it still working for me? Are other people having
> problems?
>
> Cheers
>
> Mirko
>

> 2008/11/24 Arthur Kalmenson <arthur.k...@gmail.com>:

>
>
>
> > Hi Mirko,
>
> > It seems to be a namespace conflict with the new Codehaus plugin. My
> > POM did not change between Friday (when it worked) and today (when it
> > stopped working). I'm guessing that Maven checks the Codehaus plugin
> > repository by default to see if it can handle the "gwt" goal,
> finds
> > that it can and downloads it.
>
> > quadmasta on the #gwt IRC channel suggested using "mvn
> > com.totsp.gwt:maven-googlewebtoolkit2-plugin:gwt" which works fine.
> Is
> > there a way to give the gwt-maven residence over codehaus?
>
> > P.S. I checked the global settings.xml and can't find codehaus there.
>
> > --
> > Arthur Kalmenson
>
> > On Mon, Nov 24, 2008 at 11:55 AM, Mirko Nasato
> <mirko.nas...@gmail.com> wrote:
>
> >> That's weird; only plugins from org.apache.maven should be picked
> up
> >> automatically, not something from org.codehaus. What's in your
> >> pom.xml?
>

> >> 2008/11/24 Arthur Kalmenson <arthur.k...@gmail.com>:

>
> >>> I should have posted the full scanning that Maven does when it
> hasn't
> >>> downloaded the Codehaus plugin:
>
> >>> arthur@ares:~/work/upma$ mvn gwt:gwt
> >>> [INFO] Scanning for projects...
> >>> [INFO] Searching repository for plugin with prefix: 'gwt'.
> >>> [INFO] artifact org.codehaus.mojo:gwt-maven-plugin: checking for
> >>> updates from gwt-maven-plugins
> >>> [INFO] artifact org.codehaus.mojo:gwt-maven-plugin: checking for
> >>> updates from central
> >>> Downloading:
>

> http://repo1.maven.org/maven2/org/codehaus/mojo/gwt-maven-plugin/1.0/...>>> 7K downloaded

[Darren Hartford]

gwtmaven +1 (matches the project name) --- On Tue, 11/25/08, Charlie Collins <charlie...@gmail.com> wrote:

[jie...@gmail.com]

While we're at it, then why not change the somewhat misnamed 'gwt'
task to be 'launch' or 'hosted' or 'hosted-mode'; so we'd have: mvn
gwtmaven:launch

My motive is that we're about to force everyone to re-learn how to
launch, we may as well clear out the entire garage of target names,
etc. :-)

-jesse

[Charlie Collins]

I'm down with renaming the "shell" goal, sure, but how about "shell"
or "runshell" or something rather than "launch"?

mvn gwtmaven:shell
mvn gwtmaven package
mvn gwtmaven test

etc

?

On Nov 25, 10:14 am, jie...@gmail.com wrote:
> While we're at it, then why not change the somewhat misnamed 'gwt'
> task to be 'launch' or 'hosted' or 'hosted-mode'; so we'd have: mvn
> gwtmaven:launch
>
> My motive is that we're about to force everyone to re-learn how to
> launch, we may as well clear out the entire garage of target names,
> etc. :-)
>
> -jesse
>
> On Tue, Nov 25, 2008 at 10:06 AM, Darren Hartford
>

[Arthur Kalmenson]

"mvn gwtmaven:shell" looks good to me, or "mvn gwtmaven:hosted" is good too.

I'm very unhappy with how the codehaus programmers did this. They
should have tried to work with this project and combine efforts
instead of going on their own and then using the same goal. Very
frustrating....

--
Arthur Kalmenson

[Mirko Nasato]

I've tried to digest the idea of changing the prefix for a few hours
now, but it still doesn't go down well with me.

Personally I would rather keep 'gwt' and add a pluginGroup to my
settings.xml. We (in my office) already have a gwt section in
settings.xml to declare a gwt.platform variable anyway.

If there really is no other option than changing the prefix, then
honestly I would avoid anything with 'maven' in it. I mean: all maven
plugins have 'maven' in their name, but that's not a good reason to
have it in the prefix as well.

I'd rather use 'tgwt' ('t' for TotSP, whatever that means ;-) or
something similarly short.

Cheers

Mirko

2008/11/25 Arthur Kalmenson <arthu...@gmail.com>:

[Charlie Collins]

It is a bit frustrating that the codehaus project clobbered us, but to
be honest I am not really sure they knew they were doing it. In fact
I doubt they did. Someone did add an issue to their tracker back when
about the conflict, so they knew about that, but I am not sure they
understood that when their plugin went into central it would
automatically usurp outs. Anyway, even though it's annoying, I am
sure it wasn't malicious.

On Nov 25, 2:08 pm, "Arthur Kalmenson" <arthur.k...@gmail.com> wrote:
> "mvn gwtmaven:shell" looks good to me, or "mvn gwtmaven:hosted" is good too.
>
> I'm very unhappy with how the codehaus programmers did this. They
> should have tried to work with this project and combine efforts
> instead of going on their own and then using the same goal. Very
> frustrating....
>
> --
> Arthur Kalmenson
>
> On Tue, Nov 25, 2008 at 12:47 PM, Charlie Collins
>

[Charlie Collins]

I don't think anyone likes the idea of changing the prefix, but I
think we have to, telling everyone to do their own "pluginGroup" is
going to be a bigger pain than just changing the prefix, I think (if
we don't change we will be constantly explaining this).

How about "gwtm"? Short for the name of the project "GWT-Maven".

Oh, and TotSP stands for "Temple of the Screaming Penguin" (screaming-
penguin.com) - my blog/personal projects site that I so cleverly named
about 10 years ago ;).

On Nov 25, 3:18 pm, "Mirko Nasato" <mirko.nas...@gmail.com> wrote:
> I've tried to digest the idea of changing the prefix for a few hours
> now, but it still doesn't go down well with me.
>
> Personally I would rather keep 'gwt' and add a pluginGroup to my
> settings.xml. We (in my office) already have a gwt section in
> settings.xml to declare a gwt.platform variable anyway.
>
> If there really is no other option than changing the prefix, then
> honestly I would avoid anything with 'maven' in it. I mean: all maven
> plugins have 'maven' in their name, but that's not a good reason to
> have it in the prefix as well.
>
> I'd rather use 'tgwt' ('t' for TotSP, whatever that means ;-) or
> something similarly short.
>
> Cheers
>
> Mirko
>

> 2008/11/25 Arthur Kalmenson <arthur.k...@gmail.com>:

[Mirko Nasato]

'spgwt' then, for the Screaming Penguin GWT plugin. :)

2008/11/25 Charlie Collins <charlie...@gmail.com>:

>
> I don't think anyone likes the idea of changing the prefix, but I
> think we have to, telling everyone to do their own "pluginGroup" is

> going to be a bigger pain than just changing the prefix, I think (if.

[Arthur Kalmenson]

I'm really fine with any prefix change, just as long as I don't have
to launch it with the current full package name :)

--
Arthur Kalmenson

[christian.posta]

Has this prefix been changed?

On Nov 27, 7:21 am, "Arthur Kalmenson" <arthur.k...@gmail.com> wrote:
> I'm really fine with any prefix change, just as long as I don't have
> to launch it with the current full package name :)
>
> --
> Arthur Kalmenson
>
> On Tue, Nov 25, 2008 at 3:58 PM, Charlie Collins
>

[Charlie Collins]

Not yet no, the issue is still open and there have been no releases.
In the meantime you should be able to use the fully qualified name (as
per the FAQ), it's more verbose, but it should work fine.

http://code.google.com/p/gwt-maven/wiki/M2FAQ

On Dec 1, 8:16 pm, "christian.posta" <christian.po...@gmail.com>
wrote: