Group :: Desenvolvimento/Outros
RPM: buildnumber-maven-plugin
Principal Changelog Spec Patches Sources Download Gear Bugs e FR Repocop
A versão atual: 1.3-alt1_17jpp11
Data da compilação: 31 maio 2021, 23:24 ( 151.5 weeks ago )
Tamanho:: 93.44 Kb
Home page: http://svn.codehaus.org/mojo/tags/buildnumber-m…
Licença: MIT and ASL 2.0
Sumário: Build Number Maven Plugin
Descrição:
Lista dos contribuidores Lista dos rpms provida por esta srpm:
ACL:
Data da compilação: 31 maio 2021, 23:24 ( 151.5 weeks ago )
Tamanho:: 93.44 Kb
Home page: http://svn.codehaus.org/mojo/tags/buildnumber-m…
Licença: MIT and ASL 2.0
Sumário: Build Number Maven Plugin
Descrição:
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, and in particular, at this time, from svn. You can then place that
build number in metadata, which can be accessed from your app, if desired.
The mojo also has a couple of extra functions to ensure you get the proper
build number. First, your local repository is checked to make sure it is
up to date. Second, your local repository is automatically updated, so that
you get the latest build number. Both these functions can be suppressed,
if desired.
Optionally, you can configure this mojo to produce a revision based on a
timestamp, or on a sequence, without requiring any interaction with an
SCM system. Note that currently, the only supported SCM is subversion.
Mantenedor currente: Igor Vlasenko 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, and in particular, at this time, from svn. You can then place that
build number in metadata, which can be accessed from your app, if desired.
The mojo also has a couple of extra functions to ensure you get the proper
build number. First, your local repository is checked to make sure it is
up to date. Second, your local repository is automatically updated, so that
you get the latest build number. Both these functions can be suppressed,
if desired.
Optionally, you can configure this mojo to produce a revision based on a
timestamp, or on a sequence, without requiring any interaction with an
SCM system. Note that currently, the only supported SCM is subversion.
Lista dos contribuidores Lista dos rpms provida por esta srpm:
- buildnumber-maven-plugin
- buildnumber-maven-plugin-javadoc