Am Samstag, 30. September 2017, 17:13:20 CEST schrieb Stefan Bruens:
On Samstag, 30. September 2017 16:59:48 CEST Axel
Freitag, 22. September 2017 um 16:06 Uhr
Von: "Dominique Leuenberger / DimStar" <dimstar(a)opensuse.org>
Betreff: Re: [opensuse-packaging] Java-build on TW fails suddenly:
error: Source option 1.5 is no longer supported. Use 1.6 or later.>
On Fri, 2017-09-22 at 16:25 +0300, Axel Braun wrote:
> As Robert already mentioned, in most cases
switching the source and
> target version to 1.6 is sufficient; in some cases, the code needs
> patching if it actually violates Java 6 conventions.
The current build already requires java6 or higher, that's the funny
Maybe - but the source claims to be a java 1.5 source (or at least in
parts); up to java 8 (1.8, 1.5 sources were still interpreted; but it's
the time when Java wants to start cleaning up;
Yes , the source claimed it it 1.5. I shifted this to 1.6, and immediately
get a different error (rest of the source unchanged):
[ 42s] [javac]
jity/contrib/util/LogFactory.java:33: error: unmappable character for
encoding ASCII [ 42s] [javac] Attribution Information: Attribution
Copyright Notice: Copyright ? 2006, 2007 [ 42s] [javac]
where is encoding US-ASCII suddenly coming from?
Apparently the file has a non-ASCII © character in it. ASCII is a subset of
UTF-8, CP1252, ISO8859-15, so most characters are fine, independent of the
source encoding and the expected encoding.
I checked the source, nearly every file has the Trademark sign in.
Either older versions just ignored badly encoded
characters or the default
encoding has changed.
Yes, thats what I'm trying to find out. Potentially there is some magic setting
in the build file to be set - but I dont know enough about Java programming for
To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org