blocks|key|443572|text|我发现了this+article，解释说由于bug+in+maven的原因，构建时间戳不会传播到过滤器。解决方法是将时间戳包装在另一个属性中：|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|443573|<properties>
+++<timestamp>${maven.build.timestamp}</timestamp>
+++<maven.build.timestamp.format>yyyy-MM-dd+HH:mm</maven.build.timestamp.format>
</properties>|code-block|syntax|javascript|443574|然后，过滤就会像预期的那样工作|443575|buildTimestamp=${timestamp}|443576|entityMap|0|LINK|mutability|MUTABLE|url|https://dzone.com/articles/stamping-version-number-and|1|https://issues.apache.org/jira/browse/MRESOURCES-99^0|4|C|0|M|C|1|0|0|0|0^^$0|@$1|2|3|4|5|6|7|W|8|@]|9|@$A|X|B|Y|1|Z]|$A|10|B|11|1|12]]|C|$]]|$1|D|3|E|5|F|7|13|8|@]|9|@]|C|$G|H]]|$1|I|3|J|5|6|7|14|8|@]|9|@]|C|$]]|$1|K|3|L|5|F|7|15|8|@]|9|@]|C|$G|H]]|$1|M|3|-4|5|6|7|16|8|@]|9|@]|C|$]]]|N|$O|$5|P|Q|R|C|$S|T]]|U|$5|P|Q|R|C|$S|V]]]]

I have discovered <a href="https://dzone.com/articles/stamping-version-number-and" rel="noreferrer">this article</a>, explaining that due to a <a href="https://issues.apache.org/jira/browse/MRESOURCES-99" rel="noreferrer">bug in maven</a>, the build timestamp does not get propagated to the filtering. The workaround is to wrap the timestamp in another property:
<pre class="lang-xml prettyprint-override"><code>&lt;properties&gt;
 &lt;timestamp&gt;${maven.build.timestamp}&lt;/timestamp&gt;
 &lt;maven.build.timestamp.format&gt;yyyy-MM-dd HH:mm&lt;/maven.build.timestamp.format&gt;
&lt;/properties&gt;
</code></pre>
Filtering then works as expected for
<pre><code>buildTimestamp=${timestamp}
</code></pre>

blocks|key|443601|text|为了丰富Stackoverflow的内容，像我一样的人，找到了这篇文章来解决${maven.build.timestamp}的“问题”。这不是maven+bug，而是可以在this+post中看到的m2e的预期行为。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|443602|因此，我相信我们不能期望解决方案被“纠正”，因为据我所知，纠正涉及概念问题。|443603|在我的例子中，我所做的就是使用这个other+post中描述的插件(buildnumber-maven-plugin)。|443604|entityMap|0|LINK|mutability|MUTABLE|url|https://bugs.eclipse.org/bugs/show_bug.cgi?id=388874#c4|1|https://stackoverflow.com/a/16675480^0|12|O|2E|9|0|0|0|Y|O|H|A|1|0^^$0|@$1|2|3|4|5|6|7|T|8|@$9|U|A|V|B|C]]|D|@$9|W|A|X|1|Y]]|E|$]]|$1|F|3|G|5|6|7|Z|8|@]|D|@]|E|$]]|$1|H|3|I|5|6|7|10|8|@$9|11|A|12|B|C]]|D|@$9|13|A|14|1|15]]|E|$]]|$1|J|3|-4|5|6|7|16|8|@]|D|@]|E|$]]]|K|$L|$5|M|N|O|E|$P|Q]]|R|$5|M|N|O|E|$P|S]]]]

In order to enrich the Stackoverflow content for others, that like me, found this post as a way to solve the "problem" of <code>${maven.build.timestamp}</code>. This is not a maven bug, but an expected behavior of m2e, as can be seen in <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=388874#c4" rel="nofollow noreferrer">this post</a>.

Therefore, I believe that we can not expect the solution to be "corrected", since, from what I understand, the correction involves conceptual issues.

In my case, what I did was use the plugin (<code>buildnumber-maven-plugin</code>) as described in this <a href="https://stackoverflow.com/a/16675480">other post</a>.

blocks|key|225492|text|我可以确认，从Maven3.x开始，{maven.build.timestamp}正在“工作”。显然，他们work+arounded了这个问题。不再需要额外的properties解决方法。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|225493|但是，要注意你的“过滤”插件(maven-resources-+plugin+)是最新的。它需要相对较新，所以如果mvn+help:effective-pom显示的是旧版本(例如:+2.6)，请将其升级到较新的版本，为我修复它，3.x例如：|225494|<plugin>
++<groupId>org.apache.maven.plugins</groupId>
++<artifactId>maven-resources-plugin</artifactId>
++<version>3.1.0</version>
</plugin>|code-block|syntax|javascript|225495|不再需要<properties><timestamp>...解决方法...|225496|在某种程度上，这也澄清了为什么它可以在IntelliJ中工作，而不是在命令行中工作。IntelliJ可能使用他们自己的“修改的/内部的”maven常量，所以它在那里工作，但不是从maven命令行。|225497|另请注意，如果您将过滤资源目录添加到您的pom，您可能还需要“重新添加”默认目录，它会丢失，例如：|225498|++<resource>
++++<directory>src/main/resources-filtered</directory>+
++++<filtering>true</filtering>
++</resource>
++<resource>
++++<directory>src/main/resources</directory>+
++</resource>|225499|注意如果你使用spring+boot作为你的父母，你必须使用@maven.build.timestamp@+instead。还要注意，如果您使用的是spring+boot，那么有一个文件META-INF/build-info.properties可以选择由spring-boot-maven-plugin创建，您可以对其进行read+(spring提供了一个BuildProperties+bean以方便阅读)。|225500|entityMap|0|LINK|mutability|MUTABLE|url|http://svn.apache.org/viewvc?view=revision&revision=1742471|1|https://stackoverflow.com/questions/35417086/maven-resource-filtering-with-spring-boot-could-not-resolve-placeholder|2|https://www.vojtechruzicka.com/spring-boot-version/^0|I|N|27|A|1H|D|0|0|1L|M|0|0|4|Q|0|0|0|0|2L|U|3K|O|4Z|F|1I|7|1|4I|4|2|0^^$0|@$1|2|3|4|5|6|7|18|8|@$9|19|A|1A|B|C]|$9|1B|A|1C|B|C]]|D|@$9|1D|A|1E|1|1F]]|E|$]]|$1|F|3|G|5|6|7|1G|8|@$9|1H|A|1I|B|C]]|D|@]|E|$]]|$1|H|3|I|5|J|7|1J|8|@]|D|@]|E|$K|L]]|$1|M|3|N|5|6|7|1K|8|@$9|1L|A|1M|B|C]]|D|@]|E|$]]|$1|O|3|P|5|6|7|1N|8|@]|D|@]|E|$]]|$1|Q|3|R|5|6|7|1O|8|@]|D|@]|E|$]]|$1|S|3|T|5|J|7|1P|8|@]|D|@]|E|$K|L]]|$1|U|3|V|5|6|7|1Q|8|@$9|1R|A|1S|B|C]|$9|1T|A|1U|B|C]|$9|1V|A|1W|B|C]]|D|@$9|1X|A|1Y|1|1Z]|$9|20|A|21|1|22]]|E|$]]|$1|W|3|-4|5|6|7|23|8|@]|D|@]|E|$]]]|X|$Y|$5|Z|10|11|E|$12|13]]|14|$5|Z|10|11|E|$12|15]]|16|$5|Z|10|11|E|$12|17]]]]

I can confirm as of Maven 3.x <code>{maven.build.timestamp}</code> is "working" now. They <a href="http://svn.apache.org/viewvc?view=revision&amp;revision=1742471" rel="noreferrer">work arounded</a> the problem, apparently. No additional <code>properties</code> workaround needed anymore.

However, be careful your "filtering" plugin (maven-resources-plugin) is up to date. It needs to be relatively new, so if <code>mvn help:effective-pom</code> shows an old version (ex: 2.6), bump it to something newer, fixed it for me, 3.x ex:

<pre><code>&lt;plugin&gt;
 &lt;groupId&gt;org.apache.maven.plugins&lt;/groupId&gt;
 &lt;artifactId&gt;maven-resources-plugin&lt;/artifactId&gt;
 &lt;version&gt;3.1.0&lt;/version&gt;
&lt;/plugin&gt;
</code></pre>

<code>&lt;properties&gt;&lt;timestamp&gt;...</code> workaround is no longer required...

This also cleared up, kind of, why it was working in IntelliJ but not the command line. IntelliJ probably uses their own "modified/internal" maven constants, so it was working there, but not from maven command line.

Also note if you add a filtering resource directory to you pom, you may need to also "re-add" the default directory, it gets lost, ex:

<pre><code> &lt;resource&gt;
 &lt;directory&gt;src/main/resources-filtered&lt;/directory&gt; &lt;!-- to get "maven.build.timestamp" into resource properties file --&gt;
 &lt;filtering&gt;true&lt;/filtering&gt;
 &lt;/resource&gt;
 &lt;resource&gt;
 &lt;directory&gt;src/main/resources&lt;/directory&gt; &lt;!-- apparently have to add this is you have the other... --&gt;
 &lt;/resource&gt;
</code></pre>

NB if you're using spring boot as your parent, you have to use @maven.build.timestamp@ <a href="https://stackoverflow.com/questions/35417086/maven-resource-filtering-with-spring-boot-could-not-resolve-placeholder">instead</a>. Also note if you're using spring boot there's a file <code>META-INF/build-info.properties</code> that is optionally created by the <code>spring-boot-maven-plugin</code> that you can <a href="https://www.vojtechruzicka.com/spring-boot-version/" rel="noreferrer">read</a> (spring provides a <code>BuildProperties</code> bean for convenience reading it).

blocks|key|225542|text|在pom项目级别添加Maven属性不会考虑正确的本地时区，因此时间戳可能会显示为错误：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|225543|<properties><timestamp>${maven.build.timestamp}</timestamp></properties>|code-block|syntax|javascript|225544|使用build-helper-maven-plugin将正确的时区和当前夏令时应用于时间戳：|225545|<build>
++++<plugins>
++++++++<plugin>
++++++++++++<groupId>org.codehaus.mojo</groupId>
++++++++++++<artifactId>build-helper-maven-plugin</artifactId>
++++++++++++<version>1.9.1</version>
++++++++++++<executions>
++++++++++++++++<execution>
++++++++++++++++++++<id>timestamp-property</id>
++++++++++++++++++++<goals>
++++++++++++++++++++++++<goal>timestamp-property</goal>
++++++++++++++++++++</goals>
++++++++++++++++++++<configuration>
++++++++++++++++++++++++<name>timestamp</name>
++++++++++++++++++++++++<pattern>yyyy-MM-dd+HH:mm:ss</pattern>
++++++++++++++++++++++++<timeZone>Europe/Zurich</timeZone>
++++++++++++++++++++</configuration>
++++++++++++++++</execution>
++++++++++++</executions>
++++++++</plugin>
+++++</plugins>
+++++<resources>
+++++++++<resource>
+++++++++++++<directory>src/main/resources</directory>
+++++++++++++<filtering>true</filtering>
+++++++++</resource>
+++++</resources>
+</build>|225546|打包时，Maven将替换/resources文件夹中的任何令牌时间戳，例如resources/version.properties：|225547|Build.timestamp=${时间戳}|225548|然后，您可以在应用程序中加载此属性文件。|225549|entityMap^0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|T|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|U|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|V|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|W|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|X|8|@]|9|@]|A|$]]|$1|O|3|P|5|6|7|Y|8|@]|9|@]|A|$]]|$1|Q|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]]|R|$]]

Adding Maven properties at the pom project level doesn't take into account correct local Timezone, so timestamp may appear wrong :

<pre><code>&lt;properties&gt;&lt;timestamp&gt;${maven.build.timestamp}&lt;/timestamp&gt;&lt;/properties&gt;
</code></pre>

Using the build-helper-maven-plugin applies the correct timezone and current daylight saving to the timestamp :

<pre><code>&lt;build&gt;
 &lt;plugins&gt;
 &lt;plugin&gt;
 &lt;groupId&gt;org.codehaus.mojo&lt;/groupId&gt;
 &lt;artifactId&gt;build-helper-maven-plugin&lt;/artifactId&gt;
 &lt;version&gt;1.9.1&lt;/version&gt;
 &lt;executions&gt;
 &lt;execution&gt;
 &lt;id&gt;timestamp-property&lt;/id&gt;
 &lt;goals&gt;
 &lt;goal&gt;timestamp-property&lt;/goal&gt;
 &lt;/goals&gt;
 &lt;configuration&gt;
 &lt;name&gt;timestamp&lt;/name&gt;
 &lt;pattern&gt;yyyy-MM-dd HH:mm:ss&lt;/pattern&gt;
 &lt;timeZone&gt;Europe/Zurich&lt;/timeZone&gt;
 &lt;/configuration&gt;
 &lt;/execution&gt;
 &lt;/executions&gt;
 &lt;/plugin&gt;
 &lt;/plugins&gt;
 &lt;resources&gt;
 &lt;resource&gt;
 &lt;directory&gt;src/main/resources&lt;/directory&gt;
 &lt;filtering&gt;true&lt;/filtering&gt;
 &lt;/resource&gt;
 &lt;/resources&gt;
 &lt;/build&gt;
</code></pre>

When packaging, Maven will replace any token timestamp in /resources folder, e.g. resources/version.properties :

build.timestamp=${timestamp}

You can then load this properties file in your Application.

I am using maven 3.0.4 and would like to make the build timestamp accessible to my application. For this, I'm putting a placeholder in a <code>.properties</code> file and let maven filter on build. While this is working fine for <code>${project.version}</code>, <code>${maven.build.timestamp}</code> is not substituted on filtering. 

The property seems to be available on build - I can use it to modify the artifact name: 

<code>&lt;finalName&gt;${project.artifactId}-${maven.build.timestamp}&lt;/finalName&gt;</code>

So why is it not available for resource filtering? And, more importantly, how do I make it accessible?

How to access maven.build.timestamp for resource filtering

我使用的是maven 3.0.4，并且希望我的应用程序可以访问构建时间戳。为此，我在.properties文件中放置了一个占位符，并让maven在构建时进行过滤。虽然这对于${project.version}工作得很好，但在过滤时${maven.build.timestamp}不会被替换。该属性似乎在构建时可用--我可...

问如何访问maven.build.timestamp进行资源过滤
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何访问maven.build.timestamp进行资源过滤EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何访问maven.build.timestamp进行资源过滤
EN