[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [jdt-dev] Building a JDT distribution
|
Stephan,
Normally I would think so but I don't know how it's compiled (i.e., how
are project-specific options respected during the export compilation?)
because the log definitely has this:
# 3/1/20 6:08:01 AM CET
# Eclipse Compiler for Java(TM) v20200130-1031, 3.21.0, Copyright IBM
Corp 2000, 2015. All rights reserved.
----------
...
33. ERROR in
C:\user-home\platform-sdk-4.14\git\eclipse.jdt.ui\org.eclipse.jdt.ui\ui\org\eclipse\jdt\internal\ui\javaeditor\codemining\JavaMethodParameterCodeMining.java
(at line 34)
text.append('…');
^^^^^
Invalid character constant
----------
So it seems that whatever encoding is used in the workspace is not the
same encoding that's used during the export compilation...
But I have no idea what's going on under the covers during this export
operation...
Regards,
Ed
On 01.03.2020 12:44, Stephan Herrmann wrote:
On 01.03.20 06:29, Ed Merks wrote:
I tried it (epxort deployable feature to a repository) but it has one
error:
. ERROR in
C:\user-home\platform-sdk-4.14\git\eclipse.jdt.ui\org.eclipse.jdt.ui\ui\org\eclipse\jdt\internal\ui\javaeditor\codemining\JavaMethodParameterCodeMining.java
(at line 34)
text.append('…');
I guess it would better if JDT's source didn't rely on the correct
encoding, i.e., UTF-8.
the project has a org.eclipse.core.resources.prefs with this:
eclipse.preferences.version=1
encoding/<project>=UTF-8
Shouldn't that suffice?
Stephan
_______________________________________________
jdt-dev mailing list
jdt-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or
unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jdt-dev
