I have been using https://github.com/aleksandr-m/gitflow-maven-plugin 
<https://github.com/aleksandr-m/gitflow-maven-plugin> and found that it works 
quite sweetly.

… and it is being actively maintained.

Cheers,

Steve C

> On 1 Mar 2018, at 12:56 am, Ben Tatham <bentat...@nanometrics.ca> wrote:
> 
> Sounds like you're using gitflow (master, develop, feature/* branches).  If
> so, we use the jgitflow-maven-plugin instead of maven-release-plugin, which
> handles these transitions and the inherent conflicts caused by the maven
> versioning.
> 
> Unfortunately, the maintainer is no longer working on it (and says he's not
> even working in java anymore), but it still works well.
> 
> https://bitbucket.org/atlassian/jgit-flow/wiki/Home
> 
> On Wed, Feb 28, 2018 at 7:18 AM Matthew Broadhead <
> matthew.broadh...@nbmlaw.co.uk> wrote:
> 
>> hi,
>> not sure if this is the correct place to ask questions about the maven
>> release plugin
>> i am trying to set my snapshots and releases properly
>> i am using git with a master branch and a development branch
>> how do i work in the snapshot on development and then tag the releases
>> to master?
>> if you know any good tutorials online that would help as i tried a few
>> but they didn't fit my case
>> 
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
>> For additional commands, e-mail: users-h...@maven.apache.org
>> 
>> --
> -- 
> Ben Tatham
> Software Architect
> 
> *Nano**metrics* *Inc.*
> 
> Ottawa * I*  Calgary  *I*  Houston  *I*  Beijing
> 
> T: +1 613 505 5065  *I*  bentat...@nanometrics.ca
> www.nanometrics.ca  *I  *www.microseismicmonitoring.com
> 
> This message is intended exclusively for the individual or entity to which
> it is addressed. This communication may contain information that is
> proprietary, privileged, confidential or otherwise legally exempt from
> disclosure. If you are not the named addressee, or have been inadvertently
> and erroneously referenced in the address line, you are not authorized to
> read, print, retain, copy or disseminate this message or any part of it. If
> you have received this message in error, please notify the sender
> immediately by e-mail and delete all copies of the message.

Reply via email to