Uploaded image for project: 'Modules'
  1. Modules
  2. MODULES-4228

Deploying an updated war file

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Open
    • Priority: Normal
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: tomcat
    • Environment:

      Linux

    • Template:
    • Epic Link:
    • Team:
      Modules
    • QA Risk Assessment:
      Needs Assessment

      Description

      The issue here revolves around Apache Tomcat taking its context root from the name of the war file and war file names needing to change to reflect the version number and the fact that the version has moved on.

      Issue MODULES-1545 discusses an issue whereby a new version of a war file fails to get deployed.

      That issue was raised in November 2014. The following month, a solution was posted by Patrick O'Dwyer. If I understand it correctly, his solution is forget about using tomcat::war and instead add the following to your Puppet code:

      staging::file {‘${name}’:
        source => ‘$war_source,
      }
       
      file { "${_deployment_path}/${_war_name}":
        source => "${::staging::path}/tomcat/${name},
      }
      

      A year later Daniel Haag proposed fixing the problem with a change to this module's war.pp file, replacing:

      staging::file { $name:
        source => $war_source,
        target => "${_deployment_path}/${_war_name}",
      }
      

      with:

      include 'staging'
      staging::file { $name:
        source => $war_source,
      } ->
        file { "${_deployment_path}/${_war_name}":
        source => "${::staging::path}/tomcat/${name}",
      }
      

      I don't understand why it hasn't made it into the current version.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned
              Reporter:
              vw Vince Webb
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Dates

                Created:
                Updated:

                  Zendesk Support