maven-release-plugin

I'm using the maven release plugin on hudson with autoVersionSubmodules set to true to automatically increment the development version in the poms. I'm wondering if there is a way to make the plugin increment the major version rather than minor version. Currently when I'm at version 1.1.0-snapshot the next version is set to 1.1.1-snapshot but ideally I would like it to change to 1.2.0-snapshot. Any idea on how to achieve this? Thanks. The maven release plugin prompts you for the values of the release version to tag and also for the next development version. You can define these to avoid

I want to deploy sources and javadocs with my snapshots. This means that I want to automize the following command: mvn clean source:jar javadoc:jar deploy Just to execute: mvn clean deploy I don't want to have javadoc/sources generation executed during the install phase (i.e. local builds). I know that source/javadoc plugins can be synchronized with the execution of the release plugin but I can't figure out how to wire it to the snapshots releases. sfussenegger <build> <plugins> <plugin> <artifactId>maven-source-plugin</artifactId> <executions> <execution> <id>attach-sources</id> <phase>deploy

I am currently enhancing the release process of our projects on Jenkins (1.430). Current release jobs Today, for one specific project, we have one job dedicated to the Release process. The complete procedure is the following: The developer who is in charge of the release changes manually the version of all the pom.xml files (in fact using mvn versions:set -DnewVersion=2.0 ) to get rid of the -SNAPSHOT . Then, he creates a tag in SVN ( http://my-svn-repo/project/tags/V_2_0 for example). Once this tag has been created, he logs on our Jenkins server, and starts a Release build. This build will

How can I get the maven-release-plugin to run without triggering the tests? I have tried -Dmaven.test.skip=true and -DskipTests and -DpreparationGoals=clean ...yet none work. Yes, I know I shouldn't release if the tests don't pass, but I don't have control over making my coworkers write reliable tests. bmargulies -Darguments="-DskipTests" is what you want, or explicitly configuring the forked executions in the pom. Engineer Dollery -Darguments="..." passes arguments to the forked maven process, but it is important to realise that there are two different switches being used here. The

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>echo-build-environment</id> <phase>validate</phase> <goals><goal>run</goal></goals> <configuration>

I have install maven in my machine. I have properly set the class-path and maven home folder. Every time I execute mvn clean install , it gives me exception. I have also tried to delete the .m2 folder but the same result. mvn -version output Apache Maven 3.3.3 (7994120775791599e205a5524ec3e0dfe41d4a06; 2015-04-22T19:57:37+08:00) Maven home: C:\maven-3 Java version: 1.7.0_45, vendor: Oracle Corporation Java home: D:\jdk170_45\jre Default locale: en_US, platform encoding: MS950 OS name: "windows 7", version: "6.1", arch: "x86", family: "windows" log for mvn -X clean install Apache Maven 3.3.3

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] ------------------------------------------------------------------------ [INFO] Checking in modified POMs... [INFO] Executing: cmd

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 source plugin from getting executed. (did not work). tried specifying the plugin phase to some non existent