Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-3715

Resource filtering fails when run from Hudson

    Details

    • Type: Bug
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Component/s: maven-plugin
    • Labels:
      None
    • Environment:
      Platform: PC, OS: Solaris
    • Similar Issues:

      Description

      This morning, we upgraded to 1.306

      We had some shell scripts being filtered during packaging. A few properties in
      them (like installation directory) were being filtered and leaving things such
      as CLASSPATH and JAVA_HOME alone (because they are not defined properties).

      As of today, those get filtered to match the values on the Hudson server. We can
      not replicate this from the command-line, even from the same machine. It only
      happens when run from within Hudson.

      We were using the maven-assembly-plugin to do the filtering. The
      maven-resources-plugin is doing the same thing.... but only from Hudson.

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              malachid malachid
            • Votes:
              1 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated: