- 浏览: 514455 次
- 性别:
- 来自: 北京
文章分类
- 全部博客 (563)
- 工作经验 (12)
- 数据库 (13)
- Servlet (10)
- Struts2 (1)
- Spring (25)
- Eclipse (5)
- Hibernate (5)
- Eclips (8)
- HTTP (7)
- J2EE (21)
- EHcache (1)
- HTML (11)
- 工具插件使用 (20)
- JPA (2)
- 杂谈 (17)
- 数据结构与算法 (3)
- Cloud Foundry (1)
- 安全 (10)
- J2SE (57)
- SQL (9)
- DB2 (6)
- 操作系统 (2)
- 设计模式 (1)
- 版本代码管理工具 (13)
- 面试 (10)
- 代码规范 (3)
- Tomcat (12)
- Ajax (5)
- 异常总结 (11)
- REST (2)
- 云 (2)
- RMI (3)
- SOA (1)
- Oracle (12)
- Javascript (20)
- jquery (7)
- JSP自定义标签 (2)
- 电脑知识 (5)
- 浏览器 (3)
- 正则表达式 (3)
- 建站解决问题 (38)
- 数据库设计 (3)
- git (16)
- log4j (1)
- 每天100行代码 (1)
- socket (0)
- java设计模式 耿祥义著 (0)
- Maven (14)
- ibatis (7)
- bug整理 (2)
- 邮件服务器 (8)
- Linux (32)
- TCP/IP协议 (5)
- java多线程并发 (7)
- IO (1)
- 网页小工具 (2)
- Flash (2)
- 爬虫 (1)
- CSS (6)
- JSON (1)
- 触发器 (1)
- java并发 (12)
- ajaxfileupload (1)
- js验证 (1)
- discuz (2)
- Mysql (14)
- jvm (2)
- MyBatis (10)
- POI (1)
- 金融 (1)
- VMWare (0)
- Redis (4)
- 性能测试 (2)
- PostgreSQL (1)
- 分布式 (2)
- Easy UI (1)
- C (1)
- 加密 (6)
- Node.js (1)
- 事务 (2)
- zookeeper (3)
- Spring MVC (2)
- 动态代理 (3)
- 日志 (2)
- 微信公众号 (2)
- IDEA (1)
- 保存他人遇到的问题 (1)
- webservice (11)
- memcached (3)
- nginx (6)
- 抓包 (1)
- java规范 (1)
- dubbo (3)
- xwiki (1)
- quartz (2)
- 数字证书 (1)
- spi (1)
- 学习编程 (6)
- dom4j (1)
- 计算机系统知识 (2)
- JAVA系统知识 (1)
- rpcf (1)
- 单元测试 (2)
- php (1)
- 内存泄漏cpu100%outofmemery (5)
- zero_copy (2)
- mac (3)
- hive (3)
- 分享资料整理 (0)
- 计算机网络 (1)
- 编写操作系统 (1)
- springboot (1)
最新评论
-
masuweng:
亦论一次OutOfMemoryError的定位与解错 -
变脸小伙:
引用[color=red][/color]百度推广中运用的技术 ...
Spring 3 mvc中返回pdf,json,xml等不同的view -
Vanillva:
不同之处是什么??
Mybatis中的like查询 -
thrillerzw:
转了。做个有理想的程序员
有理想的程序员必须知道的15件事 -
liujunhui1988:
觉得很有概括力
15 个必须知道的 Java 面试问题(2年工作经验)
源:http://maven.apache.org/maven-release/maven-release-plugin/examples/prepare-release.html
http://maven.apache.org/maven-release/maven-release-plugin/examples/branch.html
评:
Prepare a Release
Preparing a release goes through the following release phases:
Check that there are no uncommitted changes in the sources
Check that there are no SNAPSHOT dependencies
Change the version in the POMs from x-SNAPSHOT to a new version (you will be prompted for the versions to use)
Transform the SCM information in the POM to include the final destination of the tag
Run the project tests against the modified POMs to confirm everything is in working order
Commit the modified POMs
Tag the code in the SCM with a version name (this will be prompted for)
Bump the version in the POMs to a new value y-SNAPSHOT (these values will also be prompted for)
Commit the modified POMs
To prepare a release execute this command:
mvn release:prepare
Note: If an error occurs, or the process is cancelled, then running this command again will pick up from where the last one left off.
If you wish to start again, use:
mvn release:prepare -Dresume=false
Alternatively, you can use:
mvn release:clean release:prepare
Note: If any changes have been made to your source files they might need to be reverted before you restart the prepare process. You can use release:rollback to make the plugin do it for you.
Multi-module projects
You will be prompted for the version number for each module of the project. If you prefer that every module gets the same version as the parent POM, you can set the option autoVersionSubmodules to true. Now you will be asked only once for the release version and the next development version.
Generating release POMs
It is possible to generate a release-pom.xml file for each project that contains the fully resolved project used at release time as a record for later. As of the 2.0 release, this requires calling an alternate goal:
mvn release:prepare-with-pom
This goal is equivalent to the release:prepare goal, except that it requires a previous build of the project to exist to properly populate the release-pom.xml files.
Overriding the default tag name format
By default, if you do not specify a tag name, a default tag name of artifactId-version will be suggested (and if running non-interactively used).
You can specify the exact tag name to use from the command line by passing the tag property, but if you want to have the tag name generated, but just change the default pattern, you can use the tagNameFormat configuration option.
For example to have the tag name default to the version number prefixed with a v you could configure your pom like so:
<project>
[...]
<build>
[...]
<plugins>
[...]
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-release-plugin</artifactId>
<version>2.5.2</version>
<configuration>
<tagNameFormat>v@{project.version}</tagNameFormat>
</configuration>
</plugin>
[...]
</plugins>
[...]
</build>
[...]
</project>
The tagNameFormat uses @{ and } as delimiters in order to ensure that the default Maven property interpolation does not substitute the values before the version transformation has taken place.
The following properties are supported:
project.groupId which corresponds to the project's groupId.
project.artifactId which corresponds to the project's artifactId.
project.version which corresponds to the project's release version.
The project. prefix is optional and may be omitted.
----------Create a Branch
Creating a branch involves the following release phases:
Check that there are no uncommitted changes in the sources
Change the version in the POMs if you want to change it in the branch (you will be prompted for the versions to use)
Transform the SCM information in the POM to include the final destination of the tag
Commit the modified POMs
Tag the code in the SCM as a new branch with a version name (this will be prompted for)
Bump the version in the POMs if you want to change it to a new value y-SNAPSHOT (these values will also be prompted for)
Commit the modified POMs
To create a branch execute this command:
mvn release:branch -DbranchName=my-branch
By default, the POM in the new branch keeps the same version as the local working copy, and the local POM is incremented to the next revision. If you want to update versions in the new branch and not in the working copy, run:
mvn release:branch -DbranchName=my-branch -DupdateBranchVersions=true -DupdateWorkingCopyVersions=false
http://maven.apache.org/maven-release/maven-release-plugin/examples/branch.html
评:
Prepare a Release
Preparing a release goes through the following release phases:
Check that there are no uncommitted changes in the sources
Check that there are no SNAPSHOT dependencies
Change the version in the POMs from x-SNAPSHOT to a new version (you will be prompted for the versions to use)
Transform the SCM information in the POM to include the final destination of the tag
Run the project tests against the modified POMs to confirm everything is in working order
Commit the modified POMs
Tag the code in the SCM with a version name (this will be prompted for)
Bump the version in the POMs to a new value y-SNAPSHOT (these values will also be prompted for)
Commit the modified POMs
To prepare a release execute this command:
mvn release:prepare
Note: If an error occurs, or the process is cancelled, then running this command again will pick up from where the last one left off.
If you wish to start again, use:
mvn release:prepare -Dresume=false
Alternatively, you can use:
mvn release:clean release:prepare
Note: If any changes have been made to your source files they might need to be reverted before you restart the prepare process. You can use release:rollback to make the plugin do it for you.
Multi-module projects
You will be prompted for the version number for each module of the project. If you prefer that every module gets the same version as the parent POM, you can set the option autoVersionSubmodules to true. Now you will be asked only once for the release version and the next development version.
Generating release POMs
It is possible to generate a release-pom.xml file for each project that contains the fully resolved project used at release time as a record for later. As of the 2.0 release, this requires calling an alternate goal:
mvn release:prepare-with-pom
This goal is equivalent to the release:prepare goal, except that it requires a previous build of the project to exist to properly populate the release-pom.xml files.
Overriding the default tag name format
By default, if you do not specify a tag name, a default tag name of artifactId-version will be suggested (and if running non-interactively used).
You can specify the exact tag name to use from the command line by passing the tag property, but if you want to have the tag name generated, but just change the default pattern, you can use the tagNameFormat configuration option.
For example to have the tag name default to the version number prefixed with a v you could configure your pom like so:
<project>
[...]
<build>
[...]
<plugins>
[...]
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-release-plugin</artifactId>
<version>2.5.2</version>
<configuration>
<tagNameFormat>v@{project.version}</tagNameFormat>
</configuration>
</plugin>
[...]
</plugins>
[...]
</build>
[...]
</project>
The tagNameFormat uses @{ and } as delimiters in order to ensure that the default Maven property interpolation does not substitute the values before the version transformation has taken place.
The following properties are supported:
project.groupId which corresponds to the project's groupId.
project.artifactId which corresponds to the project's artifactId.
project.version which corresponds to the project's release version.
The project. prefix is optional and may be omitted.
----------Create a Branch
Creating a branch involves the following release phases:
Check that there are no uncommitted changes in the sources
Change the version in the POMs if you want to change it in the branch (you will be prompted for the versions to use)
Transform the SCM information in the POM to include the final destination of the tag
Commit the modified POMs
Tag the code in the SCM as a new branch with a version name (this will be prompted for)
Bump the version in the POMs if you want to change it to a new value y-SNAPSHOT (these values will also be prompted for)
Commit the modified POMs
To create a branch execute this command:
mvn release:branch -DbranchName=my-branch
By default, the POM in the new branch keeps the same version as the local working copy, and the local POM is incremented to the next revision. If you want to update versions in the new branch and not in the working copy, run:
mvn release:branch -DbranchName=my-branch -DupdateBranchVersions=true -DupdateWorkingCopyVersions=false
发表评论
-
Mysql经mysql连接的空闲时间超过8小时后 MySQL自动断开该连接解决方案
2016-07-06 17:16 2172源:http://www.jb51.net/artic ... -
Shell script: 获取第10+个参数
2015-11-04 14:33 475源:http://www.cnblogs.com/sheldo ... -
Maven Sonatype Nexus return 401
2015-10-23 17:18 715源:http://www.trinea.cn/dev-tool ... -
no server suitable for synchronization found
2015-10-21 16:15 1027源:http://blog.sina.com.cn/s/blo ... -
nginx超时设置
2015-10-21 14:15 690源:http://www.cnblogs.com/discus ... -
ssh 免密码登录
2015-10-12 11:26 407源:http://chenlb.iteye.com/blog/ ... -
Centos初始化java环境
2015-09-12 14:31 4941.上传 jdk jdk-7u65-linux-x64.tar ... -
ssh 远程不能执行JAVA启动脚本
2015-09-08 21:17 1296源:http://java.freesion.com/arti ... -
java ImageIO处理图像的封装
2015-09-06 10:17 364源:http://blog.csdn.net/hu_sheng ... -
解决eclipse显示jar源代码中文乱码问题
2015-08-07 16:47 576源:http://wmljava.iteye.com/blog ... -
超漂亮的纯JAVA浏览器(附源码)
2015-08-06 16:42 1202源:http://blog.csdn.net/lxf9601/ ... -
maven 手动把本地jar安装到本地仓库
2015-08-05 20:39 524源:http://jingyan.baidu.com/arti ... -
生成jar文件命令行执行main方法
2015-07-08 21:12 529源:http://stackoverflow.com/ques ... -
maven shade plugin: Invalid signature file digest for Manifest main attributes
2015-07-08 21:08 1772源:http://zhentao-li.blogspot.co ... -
maven 自动部署Tomcat错误排除
2015-05-14 12:00 590源:http://my.oschina.net/jerryhu ... -
利用MAVEN打包时,如何包含更多的资源文件
2015-04-24 10:14 379源:http://bglmmz.iteye.com/blog/ ... -
quartz的任务调度,同一个任务,在相同的时间被调用了2次
2015-02-11 13:06 638源:http://www.iteye.com/topi ... -
目前常用命令
2015-02-09 20:14 616JSON格式化 http://json.parse ... -
Maven3实战笔记09Maven的私服-Nexus常用功能
2015-02-07 21:12 415源:http://suhuanzheng7784877 ... -
Maven入门指南⑤:使用Nexus搭建Maven私服
2015-02-07 19:19 294源:http://www.cnblogs.com/luotao ...
相关推荐
Maven Release Plugin是Maven生态中的一个重要插件,用于自动化项目的版本发布流程,包括版本号更新、代码检查、打包、部署等步骤。 在Maven的Release Plugin配置中,有两个核心文件特别关键:`settings.xml`和`pom...
exec-maven-plugin是Maven生态系统中的一个插件,它允许用户在Maven构建过程中执行外部命令或脚本。这使得Maven项目可以集成更多的自定义操作,比如运行特定的脚本、调用系统命令等。本文将详细介绍exec-maven-...
Maven 使用 tomcat8-maven-plugin 插件 Maven 是一个流行的构建自动化工具,它可以帮助开发者自动完成项目的编译、测试、打包、部署等任务。 Tomcat 是一个流行的 Web 服务器,Maven 提供了一个插件 tomcat8-maven-...
java运行依赖jar包
dockerfile-maven-plugin 支持 maven 直接发布项目至 docker 镜像库
java运行依赖jar包
maven-tomcat-plugin让maven与tomcat配合得很好。它可以把应用部署到Tomcat服务器,也可以把tomcat作为内嵌服务器启动,就像jetty一样。 使用JPDA启动tomcat的远程调试功能。这样就能与eclipse配合起来,轻松地实现...
本项目是基于Java的smart-doc-maven-plugin官方maven插件设计源码,包含43个文件,其中包括27个Java源文件、7个Markdown文档、2个JSON文件、1个gitignore文件、1个LICENSE文件、1个NOTICE文件、1个PNG图片文件、1个...
maven-plugin-api-3.0.jar
java运行依赖jar包
java运行依赖jar包
解决tomcat8-maven-plugin-3.0-r1655215.jar阿里云同有的问题。放到路径org\apache\tomcat\maven\tomcat8-maven-plugin\3.0-r1655215\就可以了
maven-release-plugin-2.3.2.jar
Jenkins 中创建Maven项目安装Maven Integration plugin插件,下载该插件,在管理页面使用手动上传,安装此插件。
为了在项目中快捷方便的代码生成,将mybatis-plus-generator封装为了一个maven的插件`mybatis-plus-generator-maven-plugin。使用文档参考:https://blog.csdn.net/xiweiller/article/details/103072165
修改proguard-maven-plugin插件默认可以对proguard打包后的jar重新打包
maven的scala编译包
mybatis-plus-generator-maven-plugin-v1.0.0依赖的pom.xml,用于mybatis-plus-generator-maven-plugin-1.0.0.jar本地仓库上传时依赖使用
`maven-compiler-plugin-3.8.0-source-release` 版本是 Maven 编译插件的一个特定版本,该版本包含了对 Maven 3.x 系列的支持。这个插件的主要任务包括: 1. **源代码编译**:默认使用 JDK 的 `javac` 编译器进行 ...
jinkens支持Maven项目所需的插件Maven Integration plugin,使用Jinkens自动安装,速度太慢,在csdn下载会快很多