maven-release-plugin

Deploying assembly package with maven-release-plugin

孤街醉人 提交于 2019-11-29 22:23:48
We use Hudson and the maven-release-plugin to do the release builds. Now I have a project which contains an assembly that puts together all needed components and then packages them into a .tar.gz package with the desired directory structure. Now I'm trying to get the release-plugin to deploy this package to our Maven repository during the release:perform goal, but only the standard stuff (sources, javadoc, POM) are deployed. I've already bound the assembly goal to the maven package phase, and the .tar.gz gets build during the release, but not uploaded to the repository. Any hints what I'm

how to release a project which depends on a 3rd party SNAPSHOT project in maven

断了今生、忘了曾经 提交于 2019-11-29 20:44:57
i would like to release a snapshot project 'foo-1.0-SNAPSHOT' using the maven release plugin. The project depends on a 3rd party module 'bar-1.0-SNAPSHOT' which is not released yet. I use the option 'allowTimestampedSnapshots' in my project's pom.xml to allow timestamped snapshots but i assume that the 3rd party module (bar) is not timestamped unless i build it myself as maven still complains about unresolved SNAPSHOT dependencies. Is there a way to release the project foo regardless of dependent SNAPSHOT projects and if not how could i add a timestamp to the 3rd party project? Gareth Davis

Maven release fails due to git failure

风格不统一 提交于 2019-11-29 19:05:34
问题 I am trying to do a mvn release, but it fails due to problems with git. I have done this multiple times before without this problem, and I really don't get why/how this is happening. I first got it doing mvn release:prepare, but got around it by adding the last line shown below to my root-pom: <artifactId>maven-release-plugin</artifactId> <configuration> <preparationGoals>clean install</preparationGoals> <pushChanges>false</pushChanges> But now, when I try to do mvn release:perform, I get the

Teamcity prepare release failed due to project name got appended to FETCH URL

萝らか妹 提交于 2019-11-29 18:07:06
I am doing prepare release through Temcity using release-plugin I got below error [10:46:19][Step 2/3] [INFO] Executing: /bin/sh -c cd /home/tcagent/buildAgent/work/860f91e0ad4abff2 && git push https://username:****@testurl.com:8081/scm/myrepo/my-project-name.git/**buildConfName** refs/heads/release/release-name:refs/heads/release/release-name [10:46:19][Step 2/3] [INFO] Working directory: /home/tcagent/buildAgent/work/860f91e0ad4abff2 [Step 2/3] Failed to execute goal org.apache.maven.plugins:maven-release-plugin:2.5.3:prepare (default-cli) on project **my-project-name**: Unable to commit

Maven release:perform failure

眉间皱痕 提交于 2019-11-29 12:30:51
I am getting error when I am applying release:perform . It is unable to uploading the artifacts into nexus repository . In my SVN 3 directory :- Branch , trunk and tag. When I am applying release:prepare it executes successfully and create a tag with removing the snapshot from pom.xml. And change the trunk/pom.xml to next version with snapshot. Before prepare Trunk/pom.xml version 2.0-SNAPSHOT After prepare Trunk/pom.xml version 2.1-SNAPSHOT After prepare tags/pom.xml version 2.0 But, when I am executing release:perform it shows error. What I did wrong. I am putting my pom.xml and settings.xml

Passing arguments to Maven release build

ⅰ亾dé卋堺 提交于 2019-11-29 12:20:56
问题 I'm trying to release a library using Maven and perform a site-deploy to sourceforge (I have create an interactive shell first). The release is done by a Jenkins job (using the Maven Release Plugin for Jenkins). I tried: -X -e -Dresume=false -Dusername=puce release:prepare release:perform -Darguments="-Dusername=puce" and -X -e -Dresume=false -Dusername=puce -Darguments=-Dusername=puce release:prepare release:perform but both times the job hangs at site:deploy of the first module: [INFO] ---

Remove -SNAPSHOT from project version in pom

夙愿已清 提交于 2019-11-29 11:33:09
问题 I have a pom with the following GAV <groupId>com.company.services</groupId> <artifactId>test-branch-2</artifactId> <version>1.0.21-SNAPSHOT</version> I want to remove -SNAPSHOT from this using maven in batch mode, so I can do it with Jenkins and not have to specify anything manually. I've looked at the documentation for version:set but all the options offer me an interactive prompt and ask me to type a name for the version. I would prefer the versions plugin, not the release plugin. 回答1:

“You don't have a SNAPSHOT project in the reactor projects list.” when using Jenkins Maven release plugin

依然范特西╮ 提交于 2019-11-28 18:30:30
I'm using SVN, Maven 3.0.3 on the latest version of Jenkins and the Maven Release plugin. I'm trying to use the Maven release plugin (through Jenkins) do a dry run and so am executing the options … Executing Maven: -B -f /scratch/jenkins/workspace/myproject/myproject/pom.xml -DdevelopmentVersion=53.0.0-SNAPSHOT -DreleaseVersion=52.0.0 -Dusername=***** -Dpassword=********* -DskipTests -P prod -Dresume=false -DdryRun=true release:prepare But the dry run is dying with the error below … [JENKINS] Archiving /scratch/jenkins/workspace/myproject/myproject/pom.xml to /home/evotext/hudson_home/jobs

“Git fatal: ref HEAD is not a symbolic ref” while using maven release plugin

我怕爱的太早我们不能终老 提交于 2019-11-28 15:35:25
问题 I get the following error output while running the Maven release plugin prepare step i.e. mvn release:prepare --batch-mode -DreleaseVersion=1.1.2 -DdevelopmentVersion=1.2.0-SNAPSHOT -Dtag=v1.1.2 -X from an Atlassian Bamboo plan. However doing the same in the command line works fine. The full error stack is below. Any ideas how can this be solved? [ERROR] Failed to execute goal org.apache.maven.plugins:maven-release-plugin:2.4.2:prepare (default-cli) on project hpcmom: An error is occurred in

How I disable the Tag creation on Maven Release Plugin

为君一笑 提交于 2019-11-28 11:48:33
问题 I'm making my first project with Maven, and I don't wanna that the Maven create the Tag, because I don't use it. How I'll make it? Tks. 回答1: As described by the update-versions goal Update the POM versions for a project. This performs the normal version updates of the release:prepare goal without making other modifications to the SCM such as tagging. Looks like that's what you are looking for. 来源: https://stackoverflow.com/questions/18211411/how-i-disable-the-tag-creation-on-maven-release