Why gwt-dev-windows is not in Repository server like gwt-dev-mac??

[vikas.n...@gmail.com]

Why gwt-dev-windows.jar is not in Repository server like gwt-dev-mac?

gwt-dev-windows.jar is available inside a zip in gwt-windows.zip
instead of as an artifact. It cause extra effort in getting the zip
first and extracting it and than I've to install in my local
repository so that I can access it in my Pom.

[charlie...@gmail.com]

I have been out of touch of this project for a while, sorry. First
off I want to say mucho gracias to those that have been supporting and
building gwt-maven here - Bill Pugh, Thomas Recloux, Brill, others.

With that out of the way I have to ask about the current repo too. It
is a bit confusing as it stands. I do not think gwt-dev-mac should be
there at all - and that is probably why gwt-dev-windows is not there
also (the question vikas asks). It looks like Cooper (kebernet) added
gwt-dev-mac to "test something":
http://groups.google.com/group/gwt-maven-svn/browse_thread/thread/b94b79e94f950d3f/a3d07cdf1896c2c1

We need to get rid of that though, because it's confusing. Right?

Also it looks like Will added zips for all the platforms:
http://groups.google.com/group/gwt-maven-svn/browse_thread/thread/d3e51e12738918cb/105a824ef8ccc616
But they are not the specific -dev and -user and -servlet and so on
jars that we used to have, instead they are the whole thing in one
shot. Are you guys using those zip files as deps in your POMs, so that
you get all of GWT, including the native stuff, from the repo? If so,
should we clean up the rest of the duplicate mavenrepo stuff and
change the docs to reflect that?

I am still using Maven 1 for most of my projects (long story, but I
have other plugins that are still M1, and it works for me). I see
that the com.google.gwt m1 style directory in the repo still has the -
servlet/-user style jars only and does not have the new full zips.
Back in the day when I created the repo I had purposely put only the
user and servlet stuff, because the dev was not open source at the
time (and because there were issues with the native stuff - maybe
including the whole thing as a zip solves that though?). If we are
using the full zips and such in m2, and we clean it up, we probably
should update the m1 part of the repo as well (we should keep these in
sync).

Thoughts, corrections, explanations?

On May 25, 4:38 am, "vikas.n.sha...@gmail.com"

[Will Pugh]

I can answer for the zip file dependencies. They are for a feature
I'm working on for the maven 2 plugin.

Using standard dependency management, it was getting tricky to run
Continuous Integration.

I added some tasks in gwt-maven for maven2, so that it could download
the jar, unzip it and then fixup the urls. Thus, on the main line, if
you have the tasks

<goal>setup</goal>
<goal>extractGwt</goal>

Behind the scenes it will grab setup new dependencies in Maven for the
zip files, and then setup new system dependencies for the appropriate
jars + setup a gwthome varaible.

I talked a bit about it in the bug:
http://code.google.com/p/gwt-maven/issues/detail?id=22&can=2&q=

There are some things that are a little gross here. Notably, we can't
always get this setup working for non standard tasks (such as
jetty:run). I need to look into whether I can setup an M2 task that
will always run.

--Will

[Rob Jellinghaus]

Thanks Will, this is definitely helpful. It seems like this also
dovetails with the earlier (somewhat defunct) thread about how to get
GWTShell test cases running under Maven.

I'm in this exact situation right now because I'm trying to revive the
GWTJSF code -- http://unrealities.com/seamgwt -- which has been moved
into Maven. I've got it building under Maven, but the surefire target
is failing because 1) NoClassDefFoundError for GWTShell, and 2) the
project has never heard of gwt-maven :-)

I'll try this out. Has this gotten any further? Anyone gotten any
GWTShell tests to work properly with this?

Cheers!
Rob

On Jun 8, 11:34 am, "Will Pugh" <willp...@gmail.com> wrote:
> I can answer for the zip file dependencies. They are for a feature
> I'm working on for the maven 2 plugin.

>...

[Rob Jellinghaus]

Hmm, my reading of http://www.manning-sandbox.com/thread.jspa?threadID=18674&tstart=0
is that it's actually not possible to get GWTShell to run under Maven
2 at all yet, at least not without patching GWT. Looks like I'll back
off on this for a while longer.

(Charlie, it sounds like we actually met, or at least saw, each other
at the GWT hack session! I demoed the Seam / GWT / JSF stuff.)

Cheers!
Rob

On Jun 19, 12:04 am, Rob Jellinghaus <rjellingh...@gmail.com> wrote:
> Thanks Will, this is definitely helpful. It seems like this also
> dovetails with the earlier (somewhat defunct) thread about how to get
> GWTShell test cases running under Maven.
>
> I'm in this exact situation right now because I'm trying to revive the

> GWTJSF code --http://unrealities.com/seamgwt-- which has been moved

[Will Pugh]

So, I'm almost a bit embarassed to admit to this, but I added in a
rather gross hack to allow you to run GWT Test cases. What can I say,
I was desparate.

On the most recent build, if you add the the
<goal>testGwt</goal>

It will set-up the class path, and shell out the tests bypassing
SureFire. This is not a complete solution, and one I would like to
get rid of when we get some fixes that will allow us to run from
SureFire again.

This goal will look for classes beginning with GwtTest* and will pipe
the results to target/gwtTest

If you have any problems, send them off to me. Like I mentioned
earlier. This is mainly a temporary solution, because I feel naked
without unit tests.

--Will

[Mapop]

I feel your pain. I've stopped using this maven plugin and wrote a few
groovy scripts to handle compile/war/shell/unit testing b/c unit tests
don't work, among many other reasons. Any progress in the forward
direction is welcome, imho.

Go Will!

On Jun 20, 7:29 pm, "Will Pugh" <willp...@gmail.com> wrote:
> So, I'm almost a bit embarassed to admit to this, but I added in a
> rather gross hack to allow you to run GWT Test cases. What can I say,
> I was desparate.
>
> On the most recent build, if you add the the
> <goal>testGwt</goal>
>
> It will set-up the class path, and shell out the tests bypassing
> SureFire. This is not a complete solution, and one I would like to
> get rid of when we get some fixes that will allow us to run from
> SureFire again.
>
> This goal will look for classes beginning with GwtTest* and will pipe
> the results to target/gwtTest
>
> If you have any problems, send them off to me. Like I mentioned
> earlier. This is mainly a temporary solution, because I feel naked
> without unit tests.
>
> --Will
>

> On 6/19/07, Rob Jellinghaus <rjellingh...@gmail.com> wrote:
>
> > Hmm, my reading ofhttp://www.manning-sandbox.com/thread.jspa?threadID=18674&tstart=0

> > is that it's actually not possible to get GWTShell to run under Maven
> > 2 at all yet, at least not without patching GWT. Looks like I'll back
> > off on this for a while longer.
>
> > (Charlie, it sounds like we actually met, or at least saw, each other
> > at the GWT hack session! I demoed the Seam / GWT / JSF stuff.)
>
> > Cheers!
> > Rob
>
> > On Jun 19, 12:04 am, Rob Jellinghaus <rjellingh...@gmail.com> wrote:
> > > Thanks Will, this is definitely helpful. It seems like this also
> > > dovetails with the earlier (somewhat defunct) thread about how to get
> > > GWTShell test cases running under Maven.
>
> > > I'm in this exact situation right now because I'm trying to revive the

> > > GWTJSF code --http://unrealities.com/seamgwt--which has been moved

[charlie...@gmail.com]

I agree, mad props to Will.

Though, you can also patch GWT and SureFire works (but that is ugly
too, that is filed with GWT).

The testing thing, is basically the reason I am using the Maven 1.x
version of gwt-maven. With 1.x I can test, can get code coverage
(though that requires another GWT patch, see GWT issue 779), etc. The
only thing I cannot do, is pass multiple arguments to the JUnitShell
using maven.junit.jvmargs=-Dgwt.args, etc. Maven 1.x parses spaces as
the delimiter to a new option - so no go there (Maven 1.x bug filed in
2004 for this). That hasn't been a huge problem for me yet though, I
can pass -web and so on, one at a time.

On Jun 20, 7:29 pm, "Will Pugh" <willp...@gmail.com> wrote:

> So, I'm almost a bit embarassed to admit to this, but I added in a
> rather gross hack to allow you to run GWT Test cases. What can I say,
> I was desparate.
>
> On the most recent build, if you add the the
> <goal>testGwt</goal>
>
> It will set-up the class path, and shell out the tests bypassing
> SureFire. This is not a complete solution, and one I would like to
> get rid of when we get some fixes that will allow us to run from
> SureFire again.
>
> This goal will look for classes beginning with GwtTest* and will pipe
> the results to target/gwtTest
>
> If you have any problems, send them off to me. Like I mentioned
> earlier. This is mainly a temporary solution, because I feel naked
> without unit tests.
>
> --Will
>

> On 6/19/07, Rob Jellinghaus <rjellingh...@gmail.com> wrote:
>
>
>

> > Hmm, my reading ofhttp://www.manning-sandbox.com/thread.jspa?threadID=18674&tstart=0

> > is that it's actually not possible to get GWTShell to run under Maven
> > 2 at all yet, at least not without patching GWT. Looks like I'll back
> > off on this for a while longer.
>
> > (Charlie, it sounds like we actually met, or at least saw, each other
> > at the GWT hack session! I demoed the Seam / GWT / JSF stuff.)
>
> > Cheers!
> > Rob
>
> > On Jun 19, 12:04 am, Rob Jellinghaus <rjellingh...@gmail.com> wrote:
> > > Thanks Will, this is definitely helpful. It seems like this also
> > > dovetails with the earlier (somewhat defunct) thread about how to get
> > > GWTShell test cases running under Maven.
>
> > > I'm in this exact situation right now because I'm trying to revive the

> > > GWTJSF code --http://unrealities.com/seamgwt--which has been moved