Thank you very much for the kind response.
I just made several attempts according to your remarks:
1) Increasing the Heap size to 1G (it used to be 512M)--> that did not work
2) I then tried to configure the maven compiler plugin to fork--> that
did not work either
3) I also increases the maxmem of the m-c-p to 1G and with fork
activated-->still no luck :'(
Could it be that you also changed something else? Anyway, I find it very
disturbing that with 2 projects in jenkins with the exact same
configuration to the exception of their name (the one that works has a
suffix '_2'), one of them works and not the other.
Moreover, if the java compiler encounters an OOME, it should definitely
fail the build instead of silently continue. I think that if you can
find an example that can pin-point this kind of issue, you should report
it as a bug. Although, I think I have already encountered OOME in the
past and I think it failed the build.
Cheers,
Guillaume
Le 19/10/2011 15:53, bgik a écrit :
I saw the same issue this week.
It appeared after a colleague merged in a large piece of work from a branch.
The remedy for us was to increase the heap size used by maven by setting
MAVEN_OPTS.
So i suspect it's caused by some 'silent' OutOfMemory error.
If you havent tried this, trying increasing the heap size.
thanks
--
View this message in context:
http://maven.40175.n5.nabble.com/Uncompiled-classes-resulting-in-COMPILATION-ERROR-cannot-find-symbol-tp4903264p4917796.html
Sent from the Maven - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
