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 <russell.g...@oracle.com> wrote: > Do you have the following in your pom.xml? > > <properties> > <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding> > </properties> > > 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 <nesto...@gmail.com> wrote: > > > > 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 > > maven that will not take into consideration the comments? > > > > Regards, > > > > Néstor > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > >
