maven-compiler-plugin by default uses JDK's javac: it seems javac can't work
with the encoding soup you have in legacy code. If you find some feature in
javac to deal with that problem, you'll have to see how to inject the trick
into maven-compiler-plugin
because Maven, or more precisely maven-c
Yes,
The problem is that the legacy code has comments in Cp1252 and Strings in
UTF-8. The weird thing is that IDEA and JDeveloper can compile them using
their internal compilers.
Regards,
Néstor
On Tue, Aug 25, 2015 at 3:36 PM, Russell Gold
wrote:
> Do you have the following in your pom.xml?
Do you have the following in your pom.xml?
UTF-8
If not, do you know what encoding is being used in your source file?
> On Aug 25, 2015, at 4:01 PM, Néstor Boscán wrote:
>
> Hi
>
> I have a legacy code that compiles correctly using IDEA or JDeveloper. But
> if I try to use
Hi
I have a legacy code that compiles correctly using IDEA or JDeveloper. But
if I try to use maven compile it generates error because there are unknoen
characters in the comments. It looks like the legacy code has different
types of character encoding in the file. Is there a way to compile using
