I found the issue to be caused by my installation of the Java debian helper packages which rely on JAXP 1.3. Removing libjaxp1.3-java and all packages needing it (gradle-debian-helper, maven-debian-helper, etc.) fixed the issue. As I am now able to run JOSM with IcedTea-Web 1.7.1 built with default-jdk I have open the following Merge Request: https://salsa.debian.org/java-team/icedtea-web/merge_requests/4/diffs
Can you please review it? As it is the first time I update a Debian package I surely have missed/broken something. Cheers, Vincent 2018-05-08 0:51 GMT+02:00 Vincent Privat <vincent.pri...@gmail.com>: > I'm able to install the packages and launch javaws \o/ > But when launching JOSM I face a JAXP configuration error: > > javax.xml.validation.SchemaFactoryConfigurationError: Provider for class > javax.xml.validation.SchemaFactory cannot be created > at java.xml/javax.xml.validation.SchemaFactoryFinder. > findServiceProvider(SchemaFactoryFinder.java:361) > at java.xml/javax.xml.validation.SchemaFactoryFinder._newFactory( > SchemaFactoryFinder.java:218) > at java.xml/javax.xml.validation.SchemaFactoryFinder.newFactory( > SchemaFactoryFinder.java:145) > at java.xml/javax.xml.validation.SchemaFactory.newInstance( > SchemaFactory.java:246) > at org.openstreetmap.josm.data.preferences.PreferencesReader. > validateXML(PreferencesReader.java:99) > at org.openstreetmap.josm.data.preferences.PreferencesReader. > validateXML(PreferencesReader.java:87) > at org.openstreetmap.josm.data.Preferences.load(Preferences.java:498) > at org.openstreetmap.josm.data.Preferences.init(Preferences.java:603) > at org.openstreetmap.josm.gui.MainApplication.mainJOSM( > MainApplication.java:937) > at org.openstreetmap.josm.gui.MainApplication$2.processArguments( > MainApplication.java:280) > at org.openstreetmap.josm.gui.MainApplication.main( > MainApplication.java:860) > ... 6 more > Caused by: java.util.ServiceConfigurationError: > javax.xml.validation.SchemaFactory: > Provider org.apache.xerces.jaxp.validation.XMLSchemaFactory not found > at java.base/java.util.ServiceLoader.fail(ServiceLoader.java:588) > at java.base/java.util.ServiceLoader.access$200( > ServiceLoader.java:390) > at java.base/java.util.ServiceLoader$LazyClassPathLookupIterator. > nextProviderClass(ServiceLoader.java:1206) > at java.base/java.util.ServiceLoader$LazyClassPathLookupIterator. > hasNextService(ServiceLoader.java:1215) > at java.base/java.util.ServiceLoader$LazyClassPathLookupIterator. > access$1200(ServiceLoader.java:1103) > at java.base/java.util.ServiceLoader$LazyClassPathLookupIterator$1. > run(ServiceLoader.java:1262) > at java.base/java.util.ServiceLoader$LazyClassPathLookupIterator$1. > run(ServiceLoader.java:1261) > at java.base/java.security.AccessController.doPrivileged(Native > Method) > at java.base/java.util.ServiceLoader$LazyClassPathLookupIterator. > hasNext(ServiceLoader.java:1264) > at java.base/java.util.ServiceLoader$2.hasNext( > ServiceLoader.java:1294) > at java.base/java.util.ServiceLoader$3.hasNext( > ServiceLoader.java:1379) > at java.xml/javax.xml.validation.SchemaFactoryFinder$2.run( > SchemaFactoryFinder.java:350) > at java.xml/javax.xml.validation.SchemaFactoryFinder$2.run( > SchemaFactoryFinder.java:346) > at java.base/java.security.AccessController.doPrivileged(Native > Method) > at java.xml/javax.xml.validation.SchemaFactoryFinder. > findServiceProvider(SchemaFactoryFinder.java:346) > ... 16 more > > Does it speak to anyone? I'm not sure if I must install something else or > if it comes from a packaging problem. > Vincent > > 2018-05-08 0:33 GMT+02:00 Vincent Privat <vincent.pri...@gmail.com>: > >> Ah, yes they're here! I did not expect them to be built outside of source >> directory. Thanks! :) >> >> 2018-05-08 0:18 GMT+02:00 Emmanuel Bourg <ebo...@apache.org>: >> >>> Le 08/05/2018 à 00:10, Vincent Privat a écrit : >>> > Updates: the original repository now contains 1.7.1. >>> > I reworked the debian scripts in my fork: >>> > https://salsa.debian.org/don-vip-guest/icedtea-web/commit/ef >>> 0ea531f1ff83b12d7b6d7733a7fbfff100c3a7 >>> > It seems I now manage to build icedtea-web using "debuild -b -uc -us" >>> in >>> > debian directory but I don't know how to install it? The packaging >>> > tutorial tells to install the package with dpkg -i but I don't see any >>> > .deb file as a result ? >>> >>> Did you check the parent directory? This is were the .deb files land >>> usually. >>> >>> >> >
