Opened 7 years ago

Last modified 2 years ago

#15182 new enhancement

Standalone JOSM validator — at Version 6

Reported by: Don-vip Owned by: Don-vip
Priority: major Milestone: Longterm
Component: Core validator Version:
Keywords: modularization Cc:

Description (last modified by Don-vip)

During Java 9 compatibility effort (#11924) I wondered if modularization could be applied to JOSM, which currently is a big spaghetti-based monolithic jar.

A clean modular architecture would be a huge task (don't know if it would really be possible at all, as we have a lot of interwoven dependencies) but I'd like to see if we can achieve a more affordable intermediate state, where we could build a standalone version of JOSM validator that could be run as follows:

java -jar josm-validator.jar data.osm -o warnings.xml

This jar having no dependency on AWT/Swing/JavaFX. This way it could be run for example by a Java 9 server VM which does not include the java.desktop module.

It would not change anything on JOSM editor except probably some API changes, but as little as possible.

Change History (6)

comment:1 by Don-vip, 7 years ago

In 12620/josm:

see #15182 - deprecate all Main logging methods and introduce suitable replacements in Logging for most of them

comment:2 by Don-vip, 7 years ago

In 12621/josm:

see #15182 - do not print stacktrace by default for debug/trace levels, as before

comment:3 by Don-vip, 7 years ago

In 12624/josm:

see #15182 - remove unused imports

comment:4 by Don-vip, 7 years ago

In 12627/josm:

see #15182 - remove unneeded imports to Main

comment:5 by Don-vip, 7 years ago

In 12628/josm:

see #15182 - build.xml - define constants for values repeated multiple times (java version, jar filename)

comment:6 by Don-vip, 7 years ago

Description: modified (diff)
Note: See TracTickets for help on using tickets.