-
New Feature
-
Resolution: Fixed
-
Blocker
-
None
-
None
-
-
Empty show more show less
We need to restore classpath observation before going final. This was made a blocker in terms of priority. See comment from May 6 for the status on that.
– old description
We should revisit and simplify the ClasspathWatcher, in particular:
- we are concerned about performance
- we are not sure this is strictly necessary
- we could try to find another library/util to do that better? e.g.
- silly example JRebelClassChangeNotifier in freemarker
- https://github.com/ronmamo/reflections
- Guava's com.google.common.reflect.ClassPath
- thread mgmt
Additionally, currently we spawn one thread per ClasspathOrigin instance we have, i.e. per YamlConfigurationSource.
We should extract ClasspathWatcher and add a ClasspathWatcherService to manage a single thread.
Acceptance criteria
- is related to
-
MAGNOLIA-6244 Restore "relayer" function in LayeredOrigin when notifying of resource changes
- Closed