maven-release-plugin

问题 Using Maven 3.0.4. I am tasked with providing a corporate parent POM for our organization. My team will provide support for questions or issues developers have when using this POM. Often they will attach a build log to a support ticket. So, I want my corporate POM to echo the version of the corporate parent to the console with any build. I'm using the antrun plugin for this. <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-antrun-plugin</artifactId> <executions> <execution> <id

问题 I'm attempting to run the mvn release:prepare goal and it's hanging after the push. Any idea what I could be doing wrong? [INFO] [INFO] ------------------------------------------------------------------------ [INFO] [INFO] BUILD SUCCESSFUL [INFO] [INFO] ------------------------------------------------------------------------ [INFO] [INFO] Total time: 8 seconds [INFO] [INFO] Finished at: Tue Jul 13 23:54:59 PDT 2010 [INFO] [INFO] Final Memory: 55M/294M [INFO] [INFO] ---------------------------

问题 I want to be able to do something like: mvn release:branch -DbranchName=${project.version} I'm sure this won't work and I'm asking for help on how to achieve it. mvn release:branch require a branchName. I need the branchName on the command line argument taking the project version as value. My pom looks like this: <profile> <id>branch</id> <activation> <property> <name>branchName</name> </property> </activation> <build> <plugins> <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId

问题 Recently having switched source code repository for a project to GitHub from SourceForge I need to update the maven release process to match. I followed this link for configuring the "scm" section of the pom. The GitHub repository is shown here. Everything else is as it was when using SVN (for publishing to https://docs.sonatype.org/display/Repository/Sonatype+OSS+Maven+Repository+Usage+Guide#SonatypeOSSMavenRepositoryUsageGuide-4.MavenRepositories). So then I invoke mvn clean release:clean

问题 I want to perform a mvn release in batch mode and without having to enter the password. This is my configuration: pom.xml ... <properties> <project.scm.id>my-scm-server</project.scm.id> </properties> <scm> <developerConnection>scm:git:ssh://jenkins@192.168.10.10/repos/git/myrepo.git</developerConnection> <tag>HEAD</tag> </scm> ... settings.xml <servers> <server> <id>my-scm-server</id> <username>root</username> <privateKey>/jenkins/.ssh/id_rsa</privateKey> <passphrase>rootpwd</passphrase> <

问题 We have a Maven project structured in a GIT repository with the following folders: Parent project folder ------> pom.xml ------> Child 1 project folder ------> ------> pom.xml ------> Child 2 project folder ------> ------> pom.xml We are now trying to use the maven-release-plugin in order to go releases of the code. When running 'mvn release:prepare release:perform', the prepare phase works fine but when the perform phase runs we get the following error: [INFO] --- maven-release-plugin:2.0

问题 I'm trying to incorporate Jenkins Maven Release plugin with Git and the job is failing because it can't find the git executable. My git repo is setup with ssh and I can execute the Git command on the Jenkins server. I can run a build using Jenkins and everything is pulled down from the Git repo successfully. But when I try to do a release, Jenkins fails to find the git command. What am I doing wrong? Jenkins Info: Version 1.504 Git Plugin 1.2.0 Git Client Plugin 1.0.3 Running on Windows

问题 I've spent years trying to deploy libraries that use native code to Maven Central. I've run into the following problems: There weren't any good plugins for building native code using Maven. native-maven-plugin was a very rigid build system that, among other things, made it difficult to debug the resulting binaries. You'd have to manually synchronize the native-maven-plugin build system with the native IDE you use for debugging. Maven did not replace variables in deployed pom.xml files: MNG

问题 For some reason, when running maven release, it is giving me an invalid URL just for the tagging part of the push. For the pom.xml commit/push, it works fine and goes to appropriate URL. See below: [INFO] Working directory: /opt/jenkins-home/jobs/Section 4362/workspace/section4362-parent [INFO] Executing: /bin/sh -c cd "/opt/jenkins-home/jobs/Section 4362/workspace/section4362-parent" && git commit --verbose -F /tmp/maven-scm-217365030.commit '/opt/jenkins-home/jobs/Section 4362/workspace

问题 I have a project which have SCM Implementation with Subversion and now I want (have) to use ClearCase as new repository. I'm having problems with scm configuration in the pom.xml, I have something like this: ... <scm> <connection>scm:svn:http://url/to/my/repository/</connection> <developerConnection>scm:svn:http://url/to/my/repository/</developerConnection> <url>http://url/to/my/repository/</url> </scm> ... Now, I have to adapt this to ClearCase. I've been looking for information on the