id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc
14901	restrict plugin classpath	bastiK	team	"Currently, we have one joined classpath for all plugins. This means a plugin can load classes from all other plugins the user has enabled.

It would be cleaner, if access was restricted to JOSM core and all dependencies (required plugins). This is implemented in the attached patch, a separate ClassLoader for each plugin is created: It first looks up a class in JOSM core, then refers to the class loader of dependent plugins and finally in the plugin jar.

One consequence is that you can include different conflicting versions of the same library in different plugins. In general, we should aim to share libraries by creating a library plugin, but in certain situations this can be impractical or impossible."	enhancement	closed	normal	17.06	Core		fixed	plugins