Is your feature request related to a problem? Please describe.
Currently we reload the path config if the rascal.mf file changes, but if someone changes their pom (to switch to a newer version of a dependency) we keep using the old files. This causes type check errors, either due to tpl binary incompatibility problem or you are referencing a newly added/changed function.
Describe the solution you'd like
Currently we watch every RASCAL.MF file for the projects where the server is active for (see PathConfigs class).
We should:
monitor changes of relevant pom.xml files (not just pom.xml but also parent poms if part of a multi-module pom)
unregister watches in case a project is removed from the workspace.
if any event triggers, we should recalulate the path config.
Is your feature request related to a problem? Please describe. Currently we reload the path config if the rascal.mf file changes, but if someone changes their pom (to switch to a newer version of a dependency) we keep using the old files. This causes type check errors, either due to tpl binary incompatibility problem or you are referencing a newly added/changed function.
Describe the solution you'd like Currently we watch every RASCAL.MF file for the projects where the server is active for (see
PathConfigsclass).We should:
pom.xmlbut also parent poms if part of a multi-module pom)if any event triggers, we should recalulate the path config.