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

The WildFly container sets jboss.server.deploy.dir incorrectly to jboss.server.base.dir/content (instead of jboss.server.data.dir/content)

    Details

    • Type: New Feature
    • Status: Closed (View workflow)
    • Priority: Major
    • Resolution: Fixed
    • Affects versions: 1.6.10
    • Fix versions: 1.6.11
    • Components: WildFly
    • Labels:
      None

      Description

      See: https://groups.google.com/forum/#!topic/codehaus-cargo/sQk3mRDwK2o

      Current(1.6.10) and previous version of cargo-maven2-plugin has some bad behaviour with wildfly12x+ containerId.

      After starting, deploying, running tests, stopping container "content"-directory(with deployment artifacts like ears/wars) in profile(java.server.base.dir), lies directly in profile directory not under profile/data.

      For example with jboss75x containerId content directory lies under data where it belongs.

      See also Screenshots please.

      The problem is. You can not start this profile manually without further adjustments. You must now move content to data.

        Attachments

          Activity

            People

            • Assignee:
              alitokmen S. Ali Tokmen
              Reporter:
              alitokmen S. Ali Tokmen
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: