> This issue is still haunting me. The same project could be running on one
If you check the 2 stacktraces you've included below, this is an error
being emitted by javac, not Maven. You just happen to see it via Maven
as that is your build tool.
It is a bit of a pain, but can you test compiling w
This issue is still haunting me. The same project could be running on one
machine but run fine on another. Wiped repos, diffrent JDKs, OSs etc. It
fails "randomly" since there are no apparant situation left I can think of
why it should fail. But when it fails it always fails at the same place,
same
Well seems like its not solved. This time I cant trace it to usage of suns
classes, and the condition is reverse now, building the whole project
doesn't render in an error but building a part of the reactor with -rf
renders the below error which builds when building the whole project. Seems
like th
No multithread build.
Windows 7x64
changed to alwaysNew
changed to 3.0
I isolated it to there's a class using sun.misc.BASE64Decoder() and this
reference is failing the build. The other problems are a result of the same
issue with properitary usage, but easy to remove. I moved the specific code
to
with multi thread build -T x ?
which os ?
Can you try with changing value of
http://maven.apache.org/plugins/maven-compiler-plugin/compile-mojo.html#compilerReuseStrategy
to alwaysNew ?
Do you have same issues using compiler plugin 3.0 ?
2013/1/10 Henrik Eriksson :
> Hi all!
> I'm getting a
