maven-release-plugin

Maven release:prepare-with-pom non-interactive

由 血红的双手。 提交于 2019-12-06 04:43:19
问题 I'm trying to release a project with Maven. My project POM is containing -SNAPSHOT dependencies, so in order to perform the release automatically, I want to use the following maven command, based on the "maven-release-plugin" goals: mvn release:prepare-with-pom in order to prepare the project's pom.xml for releasing and resolve dependencies -SNAPSHOT versions automatically without edit them by hand. Unfortunately I found this is working only in interactive mode from command line. The idea is

maven-release-plugin deploys snapshot to archiva

由 半世苍凉 提交于 2019-12-06 02:58:50
How can I force mvn release:perform to deploy to my release and not tom my snapshot repository? release:perform always deploys SNAPSHOT versions. Which makes no sense IMHO I have in my pom.xml <groupId>com.mydomain</groupId> <artifactId>MyArtifactName</artifactId> <version>1.0.6-SNAPSHOT</version> <packaging>jar</packaging> <name>MyArtifactName</name> <url>http://maven.apache.org</url> <distributionManagement> <repository> <id>central</id> <url>http://repo.example.com/artifactory/libs-release-local</url> <name>libs-release-local</name> </repository> <snapshotRepository> <id>central</id> <url

How to release Maven multi-module project with inter-project dependencies?

由 杀马特。学长 韩版系。学妹 提交于 2019-12-06 00:43:19
问题 Lets say we have 3 layers project. DB, Business, Web and aggregating pom. Project |-DB | |-pom.xml |-Business | |-pom.xml |-pom.xml All modules are ment to be released and branched together, so Aggregator pom is configured to assign the same version to all submodules. We have the following versions: DB-0.1-SNAPSHOT Business-0.1-SNAPSHOT which depends on DB-0.1-SNAPSHOT Web-0.1-SNAPSHOT which depends on Business-0.1-SNAPSHOT When doing release:prepare , all versions updated to 0.1, but prepare

How to exclude file on maven release:prepare and release:perform?

由 浪子不回头ぞ 提交于 2019-12-05 16:49:18
I am using maven to release/tag my projects, and I am using some propery files and want mvn:prepare to exclude those under release. I tried using the following command: mvn release:prepare -DpreparationGoals="clean install" -DcheckModificationExcludeList=props.properties But it still gives me the following error: [INFO] Cannot prepare the release because you have local modifications : [props.properties:unknown] So the question is: how can ACTUALLY make maven mvn:release skip checking for certian local modifications? Thanks for your time. This feature was implemented in version 2.1 来源： https:/

How to customise the tag format of the Maven release plugin?

由 耗尽温柔 提交于 2019-12-05 14:25:04
问题 In our SVN repo, we store tags like this: trunk project_a project_b branches project_a branch_x branch_y project_b tags project_a 1.0 1.1 project_b 1.0 When I run the Maven release plugin's "prepare" goal on project A, by default it creates the tag as "tags/project_a-x.x", which does not match my tag naming scheme above. I am thus depending upon whoever does the release (i.e. a fallible human) to spot this and change the tag to "tags/project_a/x.x". How can I tell the release plugin to use

Maven release:prepare : Cannot prepare the release because you have local modifications

由 大城市里の小女人 提交于 2019-12-05 03:41:59
I'm facing a problem with continuum's release:prepare phase which fails in scm-check-modifications step with error : [ERROR] org.apache.maven.shared.release.ReleaseFailureException: Cannot prepare the release because you have local modifications : [pom.xml:modified] What i did : I commited all my changes (*.java and pom.xml) into SVN I made a build of the project in Continuum I launched the preparation of the release. I know that the scm-check-modifications calls ScmCheckModificationsPhase class that verifies that there are no local changes compared to what is on the SCM. I understand if i'm

When should mvn release be used in the project lifecycle?

由 笑着哭i 提交于 2019-12-05 00:54:27
问题 To clarify the question : I am looking for established best-practices or a pro/con analysis of known practices by project lifecycle I mean : deploy to pre-integration, integration, QA, preprod and prod environment. For some context: Our project deploys to integration and QA every week, currenlty we create a new release for each integration deployment, but this doesn't feel right. It leads to updating all the poms every week breaking dev level dependencies, forcing every dev to do a refresh of

How to handle maven versions in a multi module project?

由 时间秒杀一切 提交于 2019-12-04 13:49:42
问题 I have a maven project infrastructure like this: /trunk/all/pom.xml /trunk/all/libs/lib1/pom.xml /lib2/pom.xml ... /trunk/all/projects/p1/pom.xml /p2/pom.xml ... You see, I have a lot of libraries and a lot of projects using these libraries. All this is combined to one multi module project, because I like to import the top project into eclipse and have all my libraries and projects available at once only do a single mvn test to compile and test all my code after I've done some global

Maven release:prepare-with-pom non-interactive

由 我们两清 提交于 2019-12-04 09:52:14
I'm trying to release a project with Maven. My project POM is containing -SNAPSHOT dependencies, so in order to perform the release automatically, I want to use the following maven command, based on the "maven-release-plugin" goals: mvn release:prepare-with-pom in order to prepare the project's pom.xml for releasing and resolve dependencies -SNAPSHOT versions automatically without edit them by hand. Unfortunately I found this is working only in interactive mode from command line. The idea is that I'm wondering if this can be done without any manual interaction. I am using Bamboo as CI Server

In a Maven project, how can I automatically update the version all child modules, plus the parent?

由 ﹥＞﹥吖頭↗ 提交于 2019-12-04 07:35:11
问题 I have a multi-module project. parent POM (1.0-SNAPSHOT) |-- module1 (1.0-SNAPSHOT) |-- module2 (1.0-SNAPSHOT) `-- module3 (1.0-SNAPSHOT) When I execute mvn release:prepare it verify that parent POM has a SNAPSHOT version and all dependent modules don't have a SNAPSHOT version. How automatically update all child modules from SNAPSHOT to the next release version? I would like automatically increment version for all modules. 回答1: The release plugin can handle that. Did you check Updating POM
订阅 maven-release-plugin