Cannot compile project when using external library source directly

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Create a GWT project
2. Use an external library, but use it directly as source
3. Compile the project

What is the expected output? What do you see instead?
The project should build successfully. Instead, I get maven that ask for
more memory. Increasing memory does not solve the problem.

What version of the product are you using? On what operating system?
I tried on gwt-maven 1.5.2 and 1.5.3, with GWT 1.4.60.

Please provide any additional information below.
We have a GWT application that build without problem with maven. I added
the DatePicker from Zenika (*) as source. So under 
/src/main/java I have my package com.foo.app.* and org.zenika.*

The application compile successfully under Eclipse. My maven build no
longer compile when I use gwt-maven. I always have the following error code:

"java.lang.OutOfMemoryError: Java heap space
         [ERROR] Out of memory; to increase the amount of memory, use the
-Xmx flag at startup (java -Xmx128M
...)
[ERROR] Build failed"

Of course, I tried increasing the amount memoryof memory (using both
MAVEN_OPTS and google.webtoolkit.extrajvmargs) to no success. 

I moved the files to my package so that now everything under org.zenika.*
is now under com.foo.app.*. It then compile successfully.

(*) see http://code.google.com/p/gwt-datepicker/

Original issue reported on code.google.com by thier...@gmail.com on 15 Oct 2007 at 1:30

[GoogleCodeExporter]

I cannot reproduce this problem.  I use external source libraries all the time, 
seems
to work fine.  (You may have to use google.webtoolkit.extravmargs, that is 
common,
but once set it should provide enough mem?)

Has anyone else had this problem?  

Original comment by charlie....@gmail.com on 14 Nov 2007 at 4:22

[GoogleCodeExporter]

Did you add the library as *source* or as a jar? My problem occurs when I add 
the
library as **source**.

As for increasing the memory, I said in the issue report "Of course, I tried
increasing the amount memoryof memory (using both MAVEN_OPTS and
google.webtoolkit.extrajvmargs) to no success." So yeah, I did tried it before
submitting the issue. :)

Original comment by thier...@gmail.com on 14 Nov 2007 at 4:49

[GoogleCodeExporter]

Also, your external library source, are you importing it as a module correctly?

Original comment by keber...@gmail.com on 23 Nov 2007 at 7:56

[GoogleCodeExporter]

Yes because I can compile and run the application fine in Eclipse. It's really 
the
Maven call of GWTCompiler that is the problem

Original comment by thier...@gmail.com on 23 Nov 2007 at 8:26

[GoogleCodeExporter]

I guess I still don't really understand the issue here. I see that you tried the
google.webtoolkit.extrajvmargs property, but the reason I asked is that when I 
use
that it works. For example, if you increase the memory with extrajvmargs do you 
fill
up more memory before it bombs, or does it make no difference? 

Also, I import modules, as I stated, frequently and that works fine. However, I 
do
not understand the distinction to add a library as "source." To import a module 
in my
current project, I include the import statement in my module descriptor, and 
then
include the project JAR on the classpath as a dependency (and GWT 
module/library jars
have both source and compiled resources).  

What version of GWT maven are you using, and can you post the POM?  

Original comment by charlie....@gmail.com on 12 Dec 2007 at 1:32

[GoogleCodeExporter]

What I mean by "to add a library as 'source.'"

1) Go to the Zenika website
2) Download the DatePicker jar 
3) Extract the files from the DatePicker jar. Now since DatePicker is open 
source, 
the source from the DatePicker are available. Get all the files under src/* 
that you 
have extracted and put it into your source folder
4) Use DatePicker somewhere in your application
5) Start Maven compile

As you can see, I do not use DatePicker as an external library, I add it 
directly in 
my source!

Original comment by thier...@gmail.com on 12 Dec 2007 at 2:09

[GoogleCodeExporter]

Re: "What I mean by "to add a library as 'source.'"

Oh.  I see what you mean now, I have not tried that, no.  But, at that point 
isn't
that just another source package in YOUR module (rather than an imported 
module).  I
haven't looked into it specifically, but I have used various package/paths 
before, I
think (with no ill effects).  Seems like at that point it's just another 
package/path
in the project you are building.  I will try to play around with this a bit 
when I
get a change to get a better idea of why it might be bombing. 

Original comment by charlie....@gmail.com on 18 Dec 2007 at 2:09

[GoogleCodeExporter]

Original comment by charlie....@gmail.com on 18 Dec 2007 at 2:09

[GoogleCodeExporter]

Original comment by charlie....@gmail.com on 25 Mar 2008 at 12:21

• Changed state: Invalid

[GoogleCodeExporter]

It hapens also when add external library as jar. Is there something can be done 
to
solve this problem.

Original comment by pkleszcz...@gmail.com on 21 Apr 2008 at 6:47

[GoogleCodeExporter]

There is no problem here that I am aware of.  Adding the source from another 
module
into your module as part of the source works fine - so long as you add the 
source
path to your module definition.  And, adding JARs (so long as the JARs 
themselves
also have source, if we are talking GWT JARs), also works fine - both of these 
work
fine in my experience. (There is no way adding someone elses source could work
differently than your own source, provided configuration is correct.) 

Unless someone can demonstrate this is actually a problem, and or explain it 
better
so I understand it, it's not going to get any more attention. 

Original comment by charlie....@gmail.com on 21 Apr 2008 at 11:22

[GoogleCodeExporter]

I can verify the existence of this problem. We have a project that, when 
checked out
of svn, can be compiled just fine by me, while it can not be compiled by three 
of my
colleagues, due to that OOM Error. As far as we have been able to find, our
configurations, JVM's, etc. are identical. 

There is a workaround: increase the amount of memory available to the JVM via 
the
maven-gwt-plugin <extraJvmArgs> argument. Most other ways of increasing the 
amount of
memory available to the JVM, like directly passing arguments to maven on the 
command
line or specifying them elsewhere in the POM, will _not_ work.

Original comment by ivo.we...@gmail.com on 25 May 2008 at 12:20

[GoogleCodeExporter]

Getting an out of memory error is a different issue than a source jar not 
working
(though yes the original filing here mentions out of memory also, the primary 
filing
of this was source not working - which is still not reproducible that I am 
aware of -
and why this issue is closed as invalid).  

GWT requires a lot of ram to compile, and the compiler is launched by the shell
scripts GWT-Maven builds (which require native files and so on, doesn't work 
like a
std Java Maven project), so the *expected* and normal behavior is that you use
extraJvmArgs on the GWT-Maven plugin config to add memory - that is completely
normal. Passing args on the maven command line or such should not work, that is 
what
extraJvmArgs is for (args that get migrated into the shell scripts). 

Original comment by charlie....@gmail.com on 26 May 2008 at 2:03