假設我們需要向一些工件（jar，war等）添加內部版本號。 在這里，我想演示buildnumber-maven-plugin的用法。

這篇文章基于：

• http://mojo.codehaus.org/buildnumber-maven-plugin/usage.html
• http://www.site.lalitbhatt.com/maven-build-number-plugin
• http://blog.peterlynch.ca/2009/11/buildnumber-maven-plugin-helpful.html
• http://apollo.ucalgary.ca/tlcprojectswiki/index.php/Public/Project_Versioning_-_Best_Practices#Build_Versioning

我們有一些項目，需要在jar清單文件中包含不基于VCS（SVN，Git，Mercurial等）修訂版本的順序內部版本號。 讓我們創建適當的pom.xml文件，并實施一個小型演示以驗證結果。

生成Maven項目

$ mvn archetype:generate -DgroupId=org.halyph -DartifactId=buildNoTest\ -DarchetypeArtifactId=maven-archetype-quickstart \ -DinteractiveMode=false

創建pom.xml

<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/maven-v4_0_0.xsd"><modelversion>4.0.0</modelversion><groupid>org.halyph</groupid><artifactid>buildNoTest</artifactid><packaging>jar</packaging><version>1.0-SNAPSHOT</version><name>buildNoTest</name><url>http://maven.apache.org</url><dependencies><dependency><groupid>junit</groupid><artifactid>junit</artifactid><version>3.8.1</version><scope>test</scope></dependency></dependencies><properties><project.build.sourceencoding>UTF-8</project.build.sourceencoding></properties><!-- If you have access to scm then you can place actual url's. Otherwise with <revisionOnScmFailure /> you can give some fake URLs as follows. --><scm><connection>scm:svn:http://none</connection><developerconnection>scm:svn:https://none</developerconnection><url>scm:svn:https://none</url></scm><build><resources><resource><directory>src/main/resources</directory></resource><resource><directory>src/main/filtered-resources</directory><filtering>true</filtering></resource></resources><plugins><plugin><groupid>org.codehaus.mojo</groupid><artifactid>buildnumber-maven-plugin</artifactid><version>1.1</version><executions><execution><phase>generate-resources</phase><goals><goal>create</goal></goals></execution></executions><configuration><!-- doCheck and doUpdate actually talk to repository if it's true,Check would check that there are no local changes. Update would update it --><docheck>false</docheck><doupdate>false</doupdate><!-- This ensures that even if we are not connected to scm than alsotake the version from local .svn file --><revisiononscmfailure><!--Generate sequence build number based on:build number and timestamp --><format>Build: #{0} ({1,date})</format><items><item>buildNumber\d*</item><item>timestamp</item></items></revisiononscmfailure></configuration></plugin><plugin><groupid>org.apache.maven.plugins</groupid><artifactid>maven-jar-plugin</artifactid><version>2.1</version><configuration><archive><!-- will put the entries into META-INF/MANIFEST.MF file --><manifestentries><implementation-version>${project.version}</implementation-version><implementation-build>${buildNumber}</implementation-build></manifestentries></archive></configuration></plugin></plugins></build> </project>

創建演示應用程序以驗證結果

package org.halyph;import java.io.IOException; import java.util.ResourceBundle; import java.util.jar.Attributes; import java.util.jar.Manifest;public class App {public static void main( String[] args ) throws IOException{System.out.println('Verify Resource bundle' );// Check filtered resources based on generated build numberResourceBundle bundle = ResourceBundle.getBundle( 'build' );String msg = bundle.getString( 'build.message' );System.out.println(msg);System.out.println('\nVerify Generated MANIFEST.MF Properties' );// Check Manifest file based on generated build numberManifest mf = new Manifest();mf.read(Thread.currentThread().getContextClassLoader().getResourceAsStream('META-INF/MANIFEST.MF'));Attributes atts = mf.getMainAttributes();System.out.println('Implementation-Versio: ' + atts.getValue('Implementation-Version'));System.out.println('Implementation-Build: ' + atts.getValue('Implementation-Build'));} }

多次構建應用程序并運行

$ mvn install$ java -cp target\buildNoTest-1.0-SNAPSHOT.jar org.halyph.App Verify Resource bundle Build: #3 (Jun 27, 2012)Verify Generated MANIFEST.MF Properties Implementation-Versio: 1.0-SNAPSHOT Implementation-Build: Build: #3 (Jun 27, 2012)

摘要

我們應該通過將偽造的<scm>部分添加到pom.xml中并將<revisionOnScmFailure />添加到buildnumber-maven-plugin <configuration>中，通知buildnumber-maven-plugin我們將不使用版本控制修訂作為內部版本號。

已實現的自定義內部版本號格式，請參閱buildnumber-maven-plugin <配置> / <格式>和<配置> / <項目>。

在jar清單中添加了內部版本號，請參閱maven-jar-plugin pom.xml部分

測試生成的內部版本號是否可以正確添加到過濾的資源中

• 創建的src \ main \ filtered-resources \ build.properties文件

build.message=${buildNumber}

• 添加了資源過濾，請參見<resource>標志<filtering> true </ filtering>部分
• 演示應用程序驗證jar清單文件中的過濾資源和內部版本號

• 您可以git clone這個項目https://github.com/halyph/blog-sandbox/tree/master/Maven/blogpost_062712

  參考： Maven內部版本號插件–我們的JCG合作伙伴 Orest Ivasiv的示例用法，來自Knowledge Is Everything博客。

翻譯自: https://www.javacodegeeks.com/2012/10/maven-build-number-plugin-sample-usage.html

總結

以上是生活随笔為你收集整理的Maven内部版本号插件–用法示例的全部內容，希望文章能夠幫你解決所遇到的問題。

如果覺得生活随笔網站內容還不錯，歡迎將生活随笔推薦給好友。