+1 binding .. 1.3 in staging works on a few private projects I tested,
thank you Baptise!

On Sun, Apr 27, 2014 at 2:41 PM, Baptiste Mathus <bapti...@codehaus.org> wrote:
> Hi,
>
> I'd like to release version 1.3 of the buildnumber-maven-plugin
>
> This mojo is designed to get a unique build number for each time you build
> your project. So while your version may remain constant at 1.0-SNAPSHOT for
> many iterations until release, you will have a build number that can
> uniquely identify each build during that time. The build number is obtained
> from scm. You can then place that build number in metadata, which can be
> accessed from your app, if desired.
>
> We solved 9 issues:
> https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=12124&version=18855
>
> There are still a couple of issues left in JIRA:
> https://jira.codehaus.org/browse/MBUILDNUM-9?jql=project%20%3D%20MBUILDNUM%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20priority%20DESC
>
> Staging Repositories:
> General:  https://nexus.codehaus.org/content/groups/staging/
> Exclusive:
> https://nexus.codehaus.org/content/repositories/orgcodehausmojo-1080
>
> (Staging) Site:
> http://mojo.codehaus.org/buildnumber-maven-plugin/
>
> SCM Tag:
> https://svn.codehaus.org/mojo/tags/buildnumber-maven-plugin-1.3
>
>
>  [ ] +1
>  [ ] +0
>  [ ] -1
>
> The vote is open for 72 hours and will succeed by lazy consensus.
>
>
> Cheers
>
> Baptise

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email


Reply via email to