OpenJDK 8: error messages in console

[mlep]

Error messages are displayed in the console at startup (see logfile below)

JabRef version JabRef-4.0-dev--snapshot--2017-07-22--master--8730d02d9.jar
using

openjdk version "1.8.0_131"
OpenJDK Runtime Environment (build 1.8.0_131-8u131-b11-1~bpo8+1-b11)
OpenJDK 64-Bit Server VM (build 25.131-b11, mixed mode)

and

openjfx-8u60

on Linux Mint Debian Edition (using Cinnamon)

Steps to reproduce:

1. starts JabRef from command line

Log File

ERROR StatusLogger Unrecognized format specifier [d]
ERROR StatusLogger Unrecognized conversion specifier [d] starting at position 16 in conversion pattern.
ERROR StatusLogger Unrecognized format specifier [thread]
ERROR StatusLogger Unrecognized conversion specifier [thread] starting at position 25 in conversion pattern.
ERROR StatusLogger Unrecognized format specifier [level]
ERROR StatusLogger Unrecognized conversion specifier [level] starting at position 35 in conversion pattern.
ERROR StatusLogger Unrecognized format specifier [logger]
ERROR StatusLogger Unrecognized conversion specifier [logger] starting at position 47 in conversion pattern.
ERROR StatusLogger Unrecognized format specifier [msg]
ERROR StatusLogger Unrecognized conversion specifier [msg] starting at position 54 in conversion pattern.
ERROR StatusLogger Unrecognized format specifier [n]
ERROR StatusLogger Unrecognized conversion specifier [n] starting at position 56 in conversion pattern.
ERROR StatusLogger No log4j2 configuration file found. Using default configuration: logging only errors to the console. Set system property 'org.apache.logging.log4j.simplelog.StatusLogger.level' to TRACE to show Log4j2 internal initialization logging.
ERROR StatusLogger Unrecognized format specifier [d]
ERROR StatusLogger Unrecognized conversion specifier [d] starting at position 16 in conversion pattern.
ERROR StatusLogger Unrecognized format specifier [thread]
ERROR StatusLogger Unrecognized conversion specifier [thread] starting at position 25 in conversion pattern.
ERROR StatusLogger Unrecognized format specifier [level]
ERROR StatusLogger Unrecognized conversion specifier [level] starting at position 35 in conversion pattern.
ERROR StatusLogger Unrecognized format specifier [logger]
ERROR StatusLogger Unrecognized conversion specifier [logger] starting at position 47 in conversion pattern.
ERROR StatusLogger Unrecognized format specifier [msg]
ERROR StatusLogger Unrecognized conversion specifier [msg] starting at position 54 in conversion pattern.
ERROR StatusLogger Unrecognized format specifier [n]
ERROR StatusLogger Unrecognized conversion specifier [n] starting at position 56 in conversion pattern.
AI: INFO 24-07-2017 16:26, 19: Configuration file has been successfully found as resource
File: grouptree.fxml not found, attempting with camel case
Jul 24, 2017 4:26:18 PM javafx.fxml.FXMLLoader$ValueElement processValue
WARNING: Loading FXML document with JavaFX API of version 8.0.112 by JavaFX runtime of version 8.0.60
File: grouptree.css not found, attempting with camel case

[Siedlerchr]

@koppor This is related to your changes

The other things are not really Errors, the only thing which seems to differ from oracle:
WARNING: Loading FXML document with JavaFX API of version 8.0.112 by JavaFX runtime of version 8.0.60

[koppor]

Which changes do you mean? Can you provide me to a PR?

We did NOT merge in #3015 and I cannot remember to have changed the logging at other places, did we?

[Siedlerchr]

I thought that was already merged. But it has to do with the log libs and some gradle deps:
https://stackoverflow.com/questions/34945438/log4j2-configuration-not-found-when-running-standalone-application-builded-by-sh

[koppor]

It could be 565e19e - there, the transform(new com.github.jengelman.gradle.plugins.shadow.transformers.Transformer() hack was removed by @stefan-kolb

@Siedlerchr Could you try to revert that commit and see if that helps?

[stefan-kolb]

Hm could be, although this should work with the recent changes...

[stefan-kolb]

See TheBoegl/shadow-log4j-transformer#2

[Siedlerchr]

About the openjfx stuff, it's damn complicated to find out about the versions)
Xenial only contains 8u60, while yaketty already contains 8u102
https://packages.ubuntu.com/search?lang=de&keywords=openjfx
And for other repos it's even more weird:
https://repology.org/metapackage/openjfx/versions

[stefan-kolb]

Can you check the latest master please, it should be fixed now.

[mlep]

Indeed, no more error message!