Details

    • Type: Story
    • Status: Resolved (View workflow)
    • Priority: Medium
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: 8.9.0.0
    • Component/s: None
    • Labels:
      None
    • Sprint:
      Sprint 168
    • Story Points:
      3
    • Capitalizable:
      True

      Description

      Right now, Repose explodes the EARs every time it starts into a unique-ish directory under the deployment directory. By default, Repose doesn't clean up these exploded artifacts, and defaulting the configuration to clean those artifacts up would be a Major version change.

      Alternatively, we could always explode the artifacts into the same sub-directory under the deployment directory. The sub-directory would be named based on the hash of the artifact being exploded. This would ensure that the same sub-directory naming is used, and it would mean a new directory would be used each time a new version of Repose is installed.

      Instead of exploding each artifact into a subdirectory in a subdirectory, each artifact will be exploded into a single subdirectory below the deployment directory.

      For example:
      Old behavior:

      /var/repose/064752e6-7d04-4bd7-a48b-7ed8a769963c/f65bd8c3-4cd6-4fda-a933-a97fe7a128d8/something.jar
      /var/repose/064752e6-7d04-4bd7-a48b-7ed8a769963c/f72aaa6d-9e0b-4fb7-a6cc-ae5b52bfa515/potato.jar
      

      Expected behavior:

      /var/repose/some-hash1/something.jar
      /var/repose/some-hash2/potato.jar
      

      Questions:
      What sort of hash should we use?
      How long should we let the directory names be?

      Acceptance Criteria:

      • The sub-directories that artifacts are exploded into will be named based on the hash of the artifact being exploded instead of using a random directory name like it currently is.
      • The feature will be enabled by default (no config).

        Attachments

          Activity

            People

            • Assignee:
              damien.johnson Damien Johnson
              Reporter:
              mario.lopez Mario Lopez
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: