Re: what are some best practices for maven artifact naming when multiple code branches exist?

2015-04-18 Thread Anders Hammar
I would add a suffix to the version for each branch. For example, if trunk is 1.0.0-SNAPSHOT, feature branch A would get version 1.0.0-featureA-SNAPSHOT. /Anders On Sat, Apr 18, 2015 at 9:10 PM, Nikita Tovstoles nikita.tovsto...@gmail.com wrote: Suppose we have an app that's being developed

RE: what are some best practices for maven artifact naming when multiple code branches exist?

2015-04-18 Thread Nikita Tovstoles
and...@hammar.net Date:18/04/2015 12:35 (GMT-08:00) To: Maven Users List users@maven.apache.org Cc: Subject: Re: what are some best practices for maven artifact naming when multiple code branches exist? I would add a suffix to the version for each branch. For example, if trunk is 1.0.0-SNAPSHOT

RE: what are some best practices for maven artifact naming when multiple code branches exist?

2015-04-18 Thread Sander Verhagen
: what are some best practices for maven artifact naming when multiple code branches exist? I would add a suffix to the version for each branch. For example, if trunk is 1.0.0-SNAPSHOT, feature branch A would get version 1.0.0-featureA-SNAPSHOT. /Anders On Sat, Apr 18, 2015 at 9:10 PM, Nikita