We could use a dedicated classloader to handle all mesh classes. This would remove all classes from the current root class loader and thus avoid problems with plugins.
Currently plugins use the "parent-last" classloader policy which will cause classes to be loaded from the parent if those can't be found in the plugin. We currently use maven provided scope to avoid duplicate classes in plugins. We could get rid of this workaround if we had no classes in the parent class-loader.
One idea would be to handle mesh core itself similar to a plugin.
We could use a dedicated classloader to handle all mesh classes. This would remove all classes from the current root class loader and thus avoid problems with plugins.
Currently plugins use the "parent-last" classloader policy which will cause classes to be loaded from the parent if those can't be found in the plugin. We currently use maven
providedscope to avoid duplicate classes in plugins. We could get rid of this workaround if we had no classes in the parent class-loader.One idea would be to handle mesh core itself similar to a plugin.