maven-release-plugin

问题 I have configured a Jenkins job to release my maven project automatically. This is done by using the following: mvn --batch-mode clean release:prepare release:perform In batch mode the release version and the development version will be determined automatically. This is exactly what I want. The problem is that I want to increase the 2nd number of the version instead of the 3rd one. So when I release version 1.2.0, the next development version must be 1.3.0-SNAPSHOT. Not 1.2.1-SNAPSHOT. Adding

问题 I have a flat project structure with multiple projects. I am using Nexus for internal repository and SVN for Source code management. I am able to deploy the SNAPSHOT build of my project. In my parent pom i have added the maven release plug-in: <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-release-plugin</artifactId> <version>2.1</version> </plugin> and the distribution info: <distributionManagement> <repository> <id>releases</id> <url>http://localhost:8081/nexus

问题 I have a question about Maven, the maven-release-plugin, git integration, pom.xml's, and having pom.xml's in subdirectories of the repo's local copy rather than in the root. Here's the setup: I have a github account with a limited number of private repositories I want to (am just learning to) use Maven to organize my builds/releases I might need to create many Maven "projects", several projects per git repository Each maven project requires a "pom.xml" to define its characteristics I can't,

问题 As my team works on a given project with the source in a Mercurial repository, the repository is obviously growing in size. As such, cloning a repository over the network becomes slower and slower. Are there any techniques that are used for pruning out older commits or reducing the size of the repo to make the cloning operation faster over a slow network? (We are using TortoiseHg as the Mercurial client but that (I'm guessing) shouldn't make a difference to the solution to this problem.) 回答1:

问题 I cannot find a solution for activating some Maven profile on release:prepare and release:perform (both) goals. Something like this: <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-release-plugin</artifactId> <version>2.2.1</version> <configuration> <useReleaseProfile>false</useReleaseProfile> <goals>deploy</goals> <arguments>-Pmy-release</arguments> </configuration> </plugin> just doesn't work. I know that releaseProfiles setting works only during release:perform so I

问题 I have this project made of multiple jars and war to make an ear. I build everything in snapshot and it works great. Then I made a release for every single project and saw that the jars and the war were slightly different in size than the snapshot ones. Comparing file to file I realized that the .class files were all there, but slightly larger or bigger, nothing more than 40 bytes generally. I force compilation to use java 1.5 using this tag in Maven: <build> <pluginManagement> <plugins>

问题 I've got a Maven project that I'm trying to configure to use the maven release plugin. Part of the release process is to use the Maven GPG Plugin to sign artifacts which requires among other things, the GPG signing key passphrase to succeed. Because these builds need to be runnable in a non interactive environment, (CI-Server) these params are passed in as arguments to maven in the form of -Dgpg.passphrase=XXX For snapshot builds everything works fine; the Maven GPG Plugin sees the passed in

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

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

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