Uploaded image for project: 'Codehaus Cargo'
  1. CARGO-370

Standalone configurations with no home set should default to the same tmp directory

    Details

    • Type: Improvement
    • Status: Closed (View workflow)
    • Priority: Major
    • Resolution: Fixed
    • Affects versions: 0.8
    • Fix versions: 0.9
    • Components: Generic
    • Labels:
      None

      Description

      This was the behavior of cargo 0.7 but was changed in Cargo 0.8 and I believe we need to revert it.

      The issue is that when you start a container and you don't specify a home directory for the standalone config, cargo automatically computes a default directory in java.io.tmpdir. However it picks a different directory every time. Thus when the container has to be stopped it tries to stop it but from a different configuration directory.

        Attachments

          Issue links

            Activity

              People

              • Assignee:
                Vincent Massol (Inactive)
                Reporter:
                Vincent Massol (Inactive)
              • Votes:
                0 Vote for this issue
                Watchers:
                0 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: