1. 13 Oct, 2015 4 commits
  2. 04 Sep, 2015 1 commit
  3. 01 Sep, 2015 1 commit
  4. 11 Aug, 2015 2 commits
  5. 20 Jul, 2015 1 commit
  6. 13 Jul, 2015 3 commits
  7. 11 Jul, 2015 1 commit
  8. 04 May, 2015 5 commits
  9. 28 Apr, 2015 1 commit
  10. 21 Apr, 2015 1 commit
  11. 20 Apr, 2015 1 commit
  12. 14 Apr, 2015 4 commits
  13. 10 Apr, 2015 2 commits
  14. 03 Apr, 2015 2 commits
    • Ard Schrijvers's avatar
      CMS7-8836 fix unit test · d2daeed8
      Ard Schrijvers authored
      d2daeed8
    • Ard Schrijvers's avatar
      CMS7-8836 besides some trivial refactoring of some methods and introducing a... · 371b1a5b
      Ard Schrijvers authored
      CMS7-8836 besides some trivial refactoring of some methods and introducing a WatchFilesUtils, now we make a distinction during startup whether autoreload is enabled or not: If not enabled, the normal repository bootstrapping and PostStartupTask will be executed to import webfiles. However, when auto reload is enabled, the import will always be done from the webfiles files system directory. The logic is as follows:
       
       1) During local development, the PostStartUpTask from bootstrap to import the web files from a jar is disabled by default (see (2)). Instead, during local development start up, webfiles are always imported into the repository from local filesystem, regardless whether you restart with an existing repository or a newly created one. This guarantees that local filesystem during development is always in sync with the repository webfiles. Even if the initialize item gets a reloadonstartup with new version configured, the PostStartUpTask from bootstrapping is disabled.
       2) When from the pom.xml <project.basedir>$
       {project.basedir}
       </project.basedir> is removed, the Web File Watch gets disabled, and the initialization is done via normal bootstrapping, thus including the PostStartUpTask. The reloadonstartup logic is then also applied. This is useful for testing a new deployment locally.
      371b1a5b
  15. 02 Apr, 2015 3 commits
    • Ard Schrijvers's avatar
      CMS7-8838 log at info level : The WebFilesException that is thrown directly... · 0942d6a3
      Ard Schrijvers authored
      CMS7-8838 log at info level : The WebFilesException that is thrown directly after it will also log the message and invoke new actions. No need to log at warn level: When for example some jcr node has been deleted in the repository that happens to be a webfiles folder, then changing a file in that folder locally results in a warning being logged, while only info logging about the entire bundle being reloaded is enough
      0942d6a3
    • Ard Schrijvers's avatar
      CMS7-9035 register the watchedPaths in a WeakHashMap : Once the watchable of... · 2ac11cad
      Ard Schrijvers authored
      CMS7-9035  register the watchedPaths in a WeakHashMap : Once the watchable of a WatchKey has been removed, the WatchKey for that path can be removed. Using a weak hash map the garbage collector will take care of this. Removed also the 'previouslyRegisteredPath' check as the WatchKey for a newly created directory which was previously removed has a different hashcode/equals and will simply not match any way. Added unit test that confirms correct working wrt GC and the watchedPaths
      2ac11cad
    • Ard Schrijvers's avatar
      CMS7-9029, CMS7-9028 improved exception handling and logging. Improve the time... · e1e30776
      Ard Schrijvers authored
      CMS7-9029, CMS7-9028 improved exception handling and logging. Improve the time to keep polling for changes. In case of IOException, this is typically the result of incoming changes during processing an archive, we just continue as if nothing happened. The incoming changes will trigger new events resulting in a new archive upload. What used to happen in case of an IOException, directly a full web bundle reload would be done, which typically also failed because of file changes still coming in. The incoming file changes however trigger a reload later on any way. Hence, rather just ignore besides logging
      e1e30776
  16. 01 Apr, 2015 1 commit
  17. 09 Mar, 2015 1 commit
  18. 26 Feb, 2015 1 commit
  19. 18 Feb, 2015 2 commits
  20. 02 Feb, 2015 1 commit
  21. 30 Jan, 2015 1 commit
  22. 29 Jan, 2015 1 commit