Mailing-List: contact users-help@maven.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Maven Users List" <users@maven.apache.org>
Received-SPF: pass (athena.apache.org: domain of waynefay@gmail.com designates
 209.85.220.48 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAKDUN1tH36UHETBu34S_FAeU_9M3kfv0OjtXbng0D2BmHjQy=g@mail.gmail.com>
References: <519B773E.6040509@orprovision.com>
	<CAKDUN1tH36UHETBu34S_FAeU_9M3kfv0OjtXbng0D2BmHjQy=g@mail.gmail.com>
Date: Wed, 22 May 2013 14:37:03 -0500
Message-ID: 
 <CALy+7UnRhMBur3ZiLgX=h8FwycBmGnrCNgHnWQ_9KkREYOuf8g@mail.gmail.com>
Subject: Re: Deploy using version override
From: Wayne Fay <waynefay@gmail.com>
To: Maven Users List <users@maven.apache.org>
Cc: andy.gumbrecht@orprovision.com
Content-Type: text/plain; charset=UTF-8

> Also, your internal versioning scheme is IMHO not good. You should use a
> qualifier to identify your internally released version (keeping groupId and
> artifactId). For example (and what I use) is to include something unique to
> your organization (like the company name) and then maybe the scm revision.
> Like this:
> 5.9-ABC_r52161

The OV is (I think) his company name: OrproVision. The 1 in his OV.1
might notate the first release they've made internally (??). So, he
may be pretty close to the best practices you're suggesting.

Wayne

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org