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" <[EMAIL PROTECTED]> 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
>
> <[EMAIL PROTECTED]> wrote:
>
> > 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, [EMAIL PROTECTED] 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
>
> >> <[EMAIL PROTECTED]> wrote:
> >> > gwtmaven +1 (matches the project name)
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"gwt-maven" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/gwt-maven?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to