Need fix for GWT 1.6 Jars in Maven Repo

[Will]

Not sure who is reposponsible for the jars deployed to maven, but I am
having issues with the versions deployed there.

The 1.6.0 and 1.6.1 versions of gwt-dev and gwt-user jars contain the
source code for the javax.servlet package. The problem is the source
code has a newer timestamp than the class files. This causes the
javax.servlet classes to be recompiled and placed in our target.

Can someone fix the deployed jars to either 1) include class files
having a later timestamp or 2) contain no javax source code.

Not sure of the source code is required, the jars for version 1.5.3
didn't include any javax.servlet sources. I'm leaning toward option 2
since the classpath could contain external javax.servlet classes with
older timestamp than sources bundled in gwt jars.

[Garey]

I am also having this issue. The workaround isn't hard, but it's
annoying and I would rather not do it for every release.

Thanks,

g

[eneveu]

I had the same problem yesterday, and I stumbled on this post. Thanks
a lot for the explanation.

I opened an issue here:
http://code.google.com/p/google-web-toolkit/issues/detail?id=3439

(Will, since your post explained the problem clearly, I took it as a
basis in the issue's description (changing/adding some details), I
hope you won't mind)


I wonder if this problem only appears when using maven, or if ant-
based builds also suffer from it.

-en

On Mar 3, 3:34 pm, Garey <garey.tay...@gmail.com> wrote:
> I am also having this issue.  The workaround isn't hard, but it's
> annoying and I would rather not do it for every release.
>
> Thanks,
>
> g
>
> On Feb 26, 10:49 am, Will <wgomes.ku...@gmail.com> wrote:
>
> > Not sure who is reposponsible for the jars deployed to maven, but I am
> > having issues with the versions deployed there.
>

> > The1.6.0 and1.6.1 versions of gwt-dev and gwt-user jars contain the
> > source code for thejavax.servletpackage.  The problem is the source

> > code has a newer timestamp than the class files. This causes the

> >javax.servletclasses to be recompiled and placed in our target.

>
> > Can someone fix the deployed jars to either 1) include class files

> > having a later timestamp or 2) contain nojavaxsource code.

>
> > Not sure of the source code is required, the jars for version 1.5.3

> > didn't include anyjavax.servletsources. I'm leaning toward option 2
> > since the classpath could contain externaljavax.servletclasses with

[cyril.lakech]

still the same bug in the 1.6.4 release !

[Salvador Diaz]

I don't really think this is a bug, as you shouldn't have to include
gwt-user in your war anyway. That's what the gwt-servlet is for. Does
including the gwt dependencies in your pom in the following way solves
the problem ?

See here for the snippet: http://pastebin.com/m5960979b

I'm curious about this so let me know. Thanks

Salvador

[eneveu]

Hi Salvador,

Sorry for answering so late, I didn't check this thread in a while.

The code you posted in the pastebin is expired, but here is how we
declared our GWT dependencies:
<dependency>
<groupId>com.google.gwt</groupId>
<artifactId>gwt-servlet</artifactId>
<version>${gwtVersion}</version>
<scope>compile</scope>
</dependency>
<dependency>
<groupId>com.google.gwt</groupId>
<artifactId>gwt-user</artifactId>
<version>${gwtVersion}</version>
<scope>provided</scope>
</dependency>

I was using the googlecode GWT-Maven plug-in (not the codehaus one),
and the issue I had was that Maven saw the javax.servlet.*.java had a
more recent timestamp than the javax.servlet.*.class, and thus thought
it was a good idea to re-compile them and add them to our war (in /WEB-
INF/classes/).

Our war's lib folder did not contain gwt-user.jar, only gwt-
server.jar, since gwt-user's dependency was provided. The conflict was
thus caused by these additional classes in WEB-INF/classes/.

The GWT team fixed my issue by having the same timestamp for the .java
and .class files in javax/servlet. It seems that the fix didn't work
for Cyril and maybe some other people (where Maven re-compiles the
source files even though their timestamp is correct), but I don't know
if it is due to differences between the googlecode and codehaus gwt
maven plugins, or if it is due to some specific maven configuration.

Hope this helps!

Have a nice day,

-eneveu