我正在Eclipse 2019-09上并尝试以下操作:
我创建了一个文件src/main/resources/build/build.properties
来保存有关当前版本的一些信息:
build.version=${project.version}
build.number=${buildNumber}
build.date=${buildTimestamp}
在构建项目时,变量将被正确替换,并且目标文件夹内的文件将正确呈现。在Eclipse中更改代码(无Maven构建)时,buildNumber
被其变量名替换。
我想这与m2e过于频繁地进行过滤有关(不仅是通过菜单单击 build 时)。 buildNumber
仅在“真实”构建期间可用,因此在其他情况下不可用,因此不会被替换。
我可以告诉Maven仅在特定的构建阶段执行变量替换吗?
pom.xml
的相关摘录:
<?xml version="1.0" encoding="UTF-8"?>
<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
<modelVersion>4.0.0</modelVersion>
<groupId>123</groupId>
<artifactId>456</artifactId>
<version>789</version>
<properties>
<maven.build.timestamp.format>dd.MM.yyyy HH:mm:ss</maven.build.timestamp.format>
<buildTimestamp>${maven.build.timestamp}</buildTimestamp>
</properties>
<!-- Dummy for Build Number Plugin -->
<scm>
<connection>scm:svn:http://127.0.0.1/dummy</connection>
<developerConnection>scm:svn:https://127.0.0.1/dummy</developerConnection>
<tag>HEAD</tag>
<url>http://127.0.0.1/dummy</url>
</scm>
<build>
<finalName>${project.artifactId}-${project.version}.${buildNumber}</finalName>
<resources>
<resource>
<directory>src/main/resources</directory>
<filtering>true</filtering>
</resource>
</resources>
<plugins>
<!-- Maven Build Number Plugin -->
<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>buildnumber-maven-plugin</artifactId>
<version>1.4</version>
<executions>
<execution>
<id>buildnumber</id>
<phase>clean</phase>
<goals>
<goal>create</goal>
</goals>
</execution>
</executions>
<configuration>
<format>{0,number}</format>
<items>
<item>buildNumber</item>
</items>
<doCheck>false</doCheck>
<doUpdate>false</doUpdate>
<revisionOnScmFailure>unknownbuild</revisionOnScmFailure>
</configuration>
</plugin>
</plugins>
</build>
</project>
显示我的问题的工作示例:
<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
<modelVersion>4.0.0</modelVersion>
<groupId>org.whatever</groupId>
<artifactId>test</artifactId>
<version>0.0.1-SNAPSHOT</version>
<properties>
<maven.compiler.source>12</maven.compiler.source>
<maven.compiler.target>12</maven.compiler.target>
<project.build.sourceEncoding>Cp1252</project.build.sourceEncoding>
<maven-jar-plugin.version>3.5.0</maven-jar-plugin.version>
<maven.build.timestamp.format>dd.MM.yyyy HH:mm:ss</maven.build.timestamp.format>
<buildTimestamp>${maven.build.timestamp}</buildTimestamp>
</properties>
<!-- Dummy for Build Number Plugin -->
<scm>
<connection>scm:svn:http://127.0.0.1/dummy</connection>
<developerConnection>scm:svn:https://127.0.0.1/dummy</developerConnection>
<tag>HEAD</tag>
<url>http://127.0.0.1/dummy</url>
</scm>
<build>
<finalName>${project.artifactId}-${project.version}.${buildNumber}</finalName>
<resources>
<resource>
<directory>src/main/resources</directory>
<filtering>true</filtering>
</resource>
</resources>
<plugins>
<!-- Copy dependencies into target/lib -->
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-dependency-plugin</artifactId>
<executions>
<execution>
<id>copy-dependencies</id>
<phase>package</phase>
<goals>
<goal>copy-dependencies</goal>
</goals>
<configuration>
<outputDirectory>${project.build.directory}/lib</outputDirectory>
<overWriteReleases>false</overWriteReleases>
<overWriteSnapshots>false</overWriteSnapshots>
<overWriteIfNewer>true</overWriteIfNewer>
</configuration>
</execution>
</executions>
</plugin>
<!-- Create JAR -->
<plugin>
<artifactId>maven-assembly-plugin</artifactId>
<configuration>
<archive>
<manifest>
<mainClass>org.whatever.Main</mainClass>
</manifest>
</archive>
<descriptorRefs>
<descriptorRef>jar-with-dependencies</descriptorRef>
</descriptorRefs>
</configuration>
</plugin>
<!-- Maven Build Number Plugin -->
<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>buildnumber-maven-plugin</artifactId>
<version>1.4</version>
<executions>
<execution>
<id>buildnumber</id>
<goals>
<goal>create</goal>
</goals>
</execution>
</executions>
<configuration>
<format>{0,number}</format>
<items>
<item>buildNumber</item>
</items>
<doCheck>false</doCheck>
<doUpdate>false</doUpdate>
<revisionOnScmFailure>unknownbuild</revisionOnScmFailure>
</configuration>
</plugin>
</plugins>
</build>
</project>
仅使用sysout创建一个简单的类org.whatever.test.Main.java:
package org.whatever.test;
public class Main {
public static void main(String... args) {
System.out.println("Hey!");
}
}
并在build.properties
下创建一个src/main/resources
:
build.version=${project.version}
build.number=${buildNumber}
build.date=${buildTimestamp}
Building将内部版本号增加三倍。更改Main.java(导致重新编译)会使目标目录中build.properties
的替换版本失去内部版本号。
编辑:修复了按三递增的问题。感谢khmarbaise。仍然有替换问题。 https://maven.apache.org/plugins/maven-resources-plugin/resources-mojo.html状态
默认情况下绑定到生命周期阶段:process-resources。
即将编译。 Eclipse可能会在每次代码更改(只是猜测)上执行compile
并替换资源。在此阶段,没有buildNumber可用(我不想在每次代码更改时都增加此数字)。我找不到如何绑定到另一个阶段或采用更优雅的方式。
编辑:我考虑得越多,就越想保持这种方式。通过Maven构建会增加我的构建号。构建过程还会压缩我的类文件,库等。在目标目录内和zip文件中,现在有正确的内部版本号。更改代码会导致目标/类中的内部版本号重置为$ {buildNumber},这在技术上是正确的。我与更改代码之前所处的版本不相同,而是在不同版本之间。