maven-release-plugin

问题 I am trying to use the maven release plugin to create a released version of a Java project having Perforce as the SCM. My pom scm section is: <scm> <connection>scm:p4:myperforcehostname:1666://mydepot/mycomponent</connection> <developerConnection>scm:p4:myperforcehostname:1666://mydepot/mycomponent</developerConnection> <url>http://myperforcehostname:1666</url> </scm> Also I use the P4Maven plugin and the Maven Release Plugin: <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId

问题 I want to know what does "arguments" exactly do as release:prepare parameter and what should we set as a value for it? I've checked the description for it on release:prepare description , but I don't understand. Thanks in advance. 回答1: The release plugin may call Maven along the way, with different phases/targets/arguments specified. The -Darguments option is useful for passing arguments to those nested executions. If you typed mvn release:prepare -Dmy.var=xxx then the my.var would be defined

问题 I try this command (with dryrun to test) on my maven project : mvn release:clean release:prepare -DdryRun=true -DgenerateBackupPoms=false -Dtag=solocal-refentreprive-2.1-RC02 -DreleaseVersion=2.1-RC02 -DdevelopmentVersion=2.1-SNAPSHOT at the end, the build is success, but i have (in my commit) many pom.next / pom.tag and pom.backUp.... i don't when then (-DgenerateBackupPoms=false), if i use without dryrun i dont want push this pom... Thx, 回答1: Assuming you accept the defaults release:prepare

问题 I'm trying to install a wsdl file into a remote Maven repository so I can reference it in a CXF project as per this blog post. I'm sure it could be done manually, but I want an actual maven project so I can make use of the release plugin for tagging etc. Has anybody got experience with this? 回答1: You can use the build helper maven plugin to do this. Here is an indicative code snippet <build> ... <plugins> ... <plugin> <groupId>org.codehaus.mojo</groupId> <artifactId>build-helper-maven-plugin<

问题 I love using Maven and distributed SCMs like Mercurial (BitBucket). However as I bring my project to scale and my Hg repository grows, I am finding the Maven Release plugin more and more cumbersome to work with. The primary problem is that when a mvn release:prepare is called Maven doesn't take advantage of the distributed nature of Hg and performs a full clone of the entire repository to put into a temporary directory. The issue is very well documented by Fabrizio Giudici back in 2009 http:/

问题 When using git-1.8.5, with maven-release-plugin (tested with versions 2.4.2 and 2.3.2) with mvn (tested with versions 3.1.1 and 3.0.5), running mvn release:prepare and mvn release:prepare-with-pom fails. mvn release:prepare fails to create the commits that it's supposed to create: [maven-release-plugin] prepare for next development iteration [maven-release-plugin] prepare release foo-1.0.0 and mvn release:prepare-with-pom fails with a git error: [ERROR] Failed to execute goal org.apache.maven

问题 As per the documentation, the Maven release:perform goal checks out the project and then forks a new Maven instance to build it. For some reason the forked instance appears to ignore the user's settings.xml , which causes an error in my case because that file has the definition of a property that is used to compose the repository's URL in the parent pom. User's settings.xml Definition of a property in a "nexus" profile which is always active. <profiles> <profile> <id>nexus</id> <properties>

问题 We recently migrated from SVN to git. Beside other (unexpected) issues doing releases on git, I am wondering how to deal with the following issue: When I start a release-run on Jenkins and some developer (accidentally) pushes during the first phase of the release, the release build fails with the following error: [ERROR] Failed to execute goal org.apache.maven.plugins:maven-release-plugin:2.5.3:prepare (default-cli) on project xyz: Unable to commit files [ERROR] Provider message: [ERROR] The

问题 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

问题 I'm using Hudson with the maven-release-plugin. As you may know, the maven-release-plugin builds project in 2 steps: release:prepare , then release:perform . How should I configure Hudson to execute release:rollback in case release:perform failed? 回答1: The standard way of performing release with Hudson/Jenkins is the Jenkins M2 release plugin. It wraps the maven release plugin and automates its execution. 回答2: Short answer: don't. Turn off update (do a clean checkout each time). FWIW, in my