maven-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark Derricutt" <m...@talios.com>
Subject Re: Release plugin 2.4.2 ignores pushChanges=false
Date Thu, 26 Dec 2013 20:22:16 GMT
This is the config I use:

<plugin>
  <groupId>org.apache.maven.plugins</groupId>
  <artifactId>maven-release-plugin</artifactId>
  <version>2.4.1</version>
  <dependencies>
    <dependency>
      <groupId>org.apache.maven.scm</groupId>
      <artifactId>maven-scm-provider-gitexe</artifactId>
      <version>1.8.1</version>
    </dependency>
  </dependencies>
  <configuration>
    <autoVersionSubmodules>true</autoVersionSubmodules>
    <goals>deploy</goals>
    <pushChanges>false</pushChanges>
    <localCheckout>true</localCheckout>
  </configuration>
</plugin>

without issue. I've not yet updated to 2.4.2 tho...   I'm forcing the latest maven-scm-provider-gitexe
artifact in order to use git 1.8+ which finally brought in a breaking change, the provider
was updated some time ago to NOT use the output of "git diff" but m-r-p never uses the new
versions automatically.

I believe the two relevant options you're looking for directly are pushChanges and localCheckout
- pushChanges controls whether m-r-p will do a 'git push origin' during release after the
prepare and perform goals.

localCheckout will cause m-r-p to clone FROM your working copy into the ./target directory
when doing the release goal, if you change the former you REALLY need to change the later,
as the tags won't exist on the remote repository...

Sadly I think these options should be the default values when using git ( and.or mercurial,
darcs, bazaar etc. ) since origin is not always accessible, or maybe even not exist (yet)
- not everyone uses 'origin' as a remote name either.

Mark


On 27 Dec 2013, at 7:23, Mirko Friedenhagen wrote:

> Martijn, just a guess:
>
> - there is a setting in release:prepare for remote tagging which must be
> false as well if I remember correctly.
>
> Regards
> Mirko
> --
> Sent from my mobile
> On Dec 26, 2013 4:49 PM, "Martijn Dashorst" <martijn.dashorst@gmail.com>
> wrote:
>
>> Is it me or does the maven-release-plugin ignore the pushChanges setting?
>>
>> Running the release process actually pushes the changes to the git
>> repo. And I *really* don't want that to happen.
>>
>> Relevant configuration:
>>
>> <plugin>
>>  <groupId>org.apache.maven.plugins</groupId>
>>  <artifactId>maven-release-plugin</artifactId>
>>  <version>2.4.2</version>
>>  <inherited>true</inherited>
>>  <configuration>
>>      <pushChanges>false</pushChanges>
>>      <tagNameFormat>wicket-@{project.version}</tagNameFormat>
>>      <updateWorkingCopyVersions>false</updateWorkingCopyVersions>
>>  </configuration>
>> </plugin>
>>
>>
>> $ git --version
>> git version 1.8.5.2
>>
>> $ mvn --version
>> Apache Maven 3.1.1 (0728685237757ffbf44136acec0402957f723d9a;
>> 2013-09-17 17:22:22+0200)
>> Maven home: /usr/local/Cellar/maven/3.1.1/libexec
>> Java version: 1.7.0_45, vendor: Oracle Corporation
>> Java home:
>> /Library/Java/JavaVirtualMachines/jdk1.7.0_45.jdk/Contents/Home/jre
>> Default locale: en_US, platform encoding: UTF-8
>> OS name: "mac os x", version: "10.9.1", arch: "x86_64", family: "mac"
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>>

Mime
View raw message