maven-release-plugin

问题 I have following project structure: framework framework-parent-pom framework-something ... In the pom.xml of framework-parent-pom I have defined following plugin: <plugin> <artifactId>maven-release-plugin</artifactId> <version>2.3.2</version> <configuration> <branchBase>http://.../svn/REPO/branches/framework</branchBase> <tagBase>http://.../svn/REPO/tags/releases/framework</tagBase> <tagNameFormat>release-@{project.version}</tagNameFormat> <releaseProfiles>release</releaseProfiles> <

问题 We are using the maven release plugin on hudson and trying to automate the release process. The release:prepare works fine. When we try to do the release:perform , it fails because it tries to upload a source artifact twice to the repository. Things that I tried, removing the profile which does include the maven source plugin from the super pom ( did not work) specifying the goals on hudson for release as -P!attach-source release:prepare release:perform. Which I thought will exclude the

问题 I'm trying to use Maven release plugin 2.0 to tag the version and hopefully deploy the resulting jar to the repository. I got stuck at release:prepare , getting this cryptic error: [INFO] Checking in modified POMs... [INFO] Executing: cmd.exe /X /C "svn --non-interactive commit --file C:\Users\ME~1\AppData\Local\Temp\maven-scm-950614965.commit --targets C:\Users\ME~1\AppData\Local\Temp\maven-scm-35306-targets" [INFO] Working directory: c:\workspace\release-test-trunk [INFO] Tagging release

问题 We are getting the following error with SVN and Maven. We use maven release plugin to create a tag in svn svn: OPTIONS of 'https://XXXXXXXXX/trunk': SSL handshake failed: SSL error: bad packet length maven command use is buildnumber:create build-helper:parse-version release:prepare release:perform Any thoughts on this SSL issue? 回答1: Since the Apache Maven will use the svn client which is installed in our OS. We should ensure that our svn client is worked properly. 1.Firstly we should ensure

问题 /bin/sh: svn: command not found Caused by: org.apache.maven.plugin.MojoFailureException: Unable to check for local modifications Provider message: The svn command failed. Jenkins could not find Subversion even though the "Subversion Plugin" is already installed. 回答1: The reason for this error is that you have to define explicitly in the pom.xml that the maven-release-plugin should use svnkit. Here's how: <build> <plugins> <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven

问题 I'm trying to release a project to azure artefacts, the project pom is like this <?xml version="1.0" encoding="UTF-8"?> <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/xsd/maven-4.0.0.xsd"> <modelVersion>4.0.0</modelVersion> <parent> <groupId>groupId</groupId> <artifactId>parent</artifactId> <version>1.0.1</version> </parent> <groupId>groupId.groupId</groupId>

问题 I had to update the maven release plugin from version 2.2.1 to 2.2.2 to get around a bug, but now, when doing a maven release, the files for the new version are not uploaded to my distribution management. I have tried the following: mvn release:prepare & mvn release:perform with version 2.2.2 of the release-plugin: Uploads the new SNAPSHOT-version mvn release:prepare with version 2.2.1, mvn release:perform with version 2.2.2: Uploads the new version (which is what i want) So somehow the setup

问题 I had to update the maven release plugin from version 2.2.1 to 2.2.2 to get around a bug, but now, when doing a maven release, the files for the new version are not uploaded to my distribution management. I have tried the following: mvn release:prepare & mvn release:perform with version 2.2.2 of the release-plugin: Uploads the new SNAPSHOT-version mvn release:prepare with version 2.2.1, mvn release:perform with version 2.2.2: Uploads the new version (which is what i want) So somehow the setup

问题 I'm in the process of trying to migrate our repository from SVN to Git and I'm having trouble with the release plugin on a very large project. Problem: There are about 50+ sub-modules to this project and it tries to add all the modified poms as one 'git add -- '. This breaks the windows command line limit. Fortunately a fix was put in for this in release 1.8.1 of maven-scm-provider-gitexe however the maven-release-plugin is currently set up to use 1.7 which does not have the fix. I have tried

问题 The POM that my project inherits contains some <pluginManagement> for the release plugin that specifies some additional arguments . My question is: Is there a way to override the arguments parameter from the command line in this case? The parent POM has this: <pluginManagement> <plugin> <artifactId>maven-release-plugin</artifactId> <configuration> <arguments>-Prelease</arguments> </configuration> </plugin> </pluginManagement> Due to that the command line argument doesn't work: mvn release