Uploaded image for project: 'Dev - Nexus Repo'
  1. Dev - Nexus Repo
  2. NEXUS-10418

automatically clear the karaf bundle cache on startup



    • Type: Improvement
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 3.0.0, 3.0.1
    • Fix Version/s: 3.1.0
    • Component/s: Bootstrap
    • Labels:
    • Story Points:
    • Sprint:
      Sprint 77


      NEXUS-10014 has a good summary of the options for clearing bundle cache on startup.

      The resolution of NEXUS-10014 meant:

      • the UI installer touches a clean_cache file inside the chosen data directory so that the bundle cache is cleared on startup
      • the archive installers include a clean_cache file inside their default ( but not optimal ) data subdirectory

      According to some recent analysis we still have significant user base using the archives (zip/tgz) to install Nexus. In the use case of upgrade using the archive bundle, a user needs to edit bin/nexus.vmoptions and change the karaf.data property value to reference their existing, to be upgraded data directory. They then also need to manually create a clean_cache file there so that on startup the cache is cleared.

      This issue is about eliminating the step of creating the clean_cache file and instead, configuring Nexus to always reload the bundle cache on startup. Other than some so far reportedly insignificant startup processing of bundle caching, I haven't heard of a good reason not to do this. Implementing this aims to make the upgrade process simpler.


          Issue Links



              • Assignee:
                jtom Joe Tom
                plynch Peter Lynch
                Last Updated By:
                Peter Lynch
              • Votes:
                1 Vote for this issue
                2 Start watching this issue


                • Created:
                  Date of First Response: