Maven Resources Plugin
  1. Maven Resources Plugin
  2. MRESOURCES-99

${project.baseUri} and ${maven.build.timestamp} are not expanded by resource filtering

    Details

    • Type: Improvement Improvement
    • Status: Open Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: 2.3, 2.4
    • Fix Version/s: None
    • Component/s: interpolation
    • Labels:
      None
    • Number of attachments :
      0

      Description

      When filtering resources, $

      {project.baseUri}

      and $

      {maven.build.timestamp}

      are not expanded (remains unchanged in the output file).

        Issue Links

          Activity

          Hide
          The Alchemist added a comment - - edited

          I would close this issue, as it has been fixed, as Olivier Lamy has shown. I have confirmed that <timestamp>${maven.build.timestamp}</timestamp> works.

          Show
          The Alchemist added a comment - - edited I would close this issue, as it has been fixed, as Olivier Lamy has shown. I have confirmed that <timestamp>${maven.build.timestamp}</timestamp> works.
          Hide
          Evgeny Mandrikov added a comment -

          I'm not sure that issue should be closed, because definition of a new property - it's just a workaround for original problem.

          Show
          Evgeny Mandrikov added a comment - I'm not sure that issue should be closed, because definition of a new property - it's just a workaround for original problem.
          Hide
          Aaron Digulla added a comment -

          I agree; it worries me that some properties are visible in the POM but not in the resource plugin. What is causing this? Are there two types of properties?

          Show
          Aaron Digulla added a comment - I agree; it worries me that some properties are visible in the POM but not in the resource plugin. What is causing this? Are there two types of properties?
          Hide
          The Alchemist added a comment -

          @Aaron/@Evgeny: Yeah, I revise what I said. You guys are right: this should stay open.

          Show
          The Alchemist added a comment - @Aaron/@Evgeny: Yeah, I revise what I said. You guys are right: this should stay open.
          Hide
          Matthias Müller added a comment -

          Just ran into this issue today. It's a pity it isn't solved after more than three years
          Is backwards-compatibility to Maven 2.x important at this point?
          When upgrading to Maven 3.x, man could somehow use a

          src.main.java.org.apache.maven.model.interpolation.BuildTimestampValueSource

          https://git-wip-us.apache.org/repos/asf?p=maven.git;a=blob;f=maven-model-builder/src/main/java/org/apache/maven/model/interpolation/BuildTimestampValueSource.java

          I think someone who's familiar with building maven plugins (which excludes me ) could do this in very little time...

          Show
          Matthias Müller added a comment - Just ran into this issue today. It's a pity it isn't solved after more than three years Is backwards-compatibility to Maven 2.x important at this point? When upgrading to Maven 3.x, man could somehow use a src.main.java.org.apache.maven.model.interpolation.BuildTimestampValueSource https://git-wip-us.apache.org/repos/asf?p=maven.git;a=blob;f=maven-model-builder/src/main/java/org/apache/maven/model/interpolation/BuildTimestampValueSource.java I think someone who's familiar with building maven plugins (which excludes me ) could do this in very little time...

            People

            • Assignee:
              Unassigned
              Reporter:
              Thomas Champagne
            • Votes:
              41 Vote for this issue
              Watchers:
              35 Start watching this issue

              Dates

              • Created:
                Updated: