Uploaded image for project: 'Magnolia'
  1. Magnolia
  2. MAGNOLIA-6130

Revisit use case and approach for observing resource changes on classpath


    • Icon: New Feature New Feature
    • Resolution: Fixed
    • Icon: Blocker Blocker
    • 5.4
    • None
    • None

      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.
      • 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

              mgeljic Mikaël Geljić
              mmuehlebach Michael Mühlebach
              0 Vote for this issue
              4 Start watching this issue