Группа :: Разработка/Прочее
Пакет: buildnumber-maven-plugin
Главная Изменения Спек Патчи Sources Загрузить Gear Bugs and FR Repocop
Текущая версия: 1.3-alt1_17jpp11
Время сборки: 31 мая 2021, 23:24 ( 147.4 недели назад )
Размер архива: 93.44 Kb
Домашняя страница: http://svn.codehaus.org/mojo/tags/buildnumber-m…
Лицензия: MIT and ASL 2.0
О пакете: Build Number Maven Plugin
Описание:
Список всех майнтейнеров, принимавших участие
в данной и/или предыдущих сборках пакета: Список rpm-пакетов, предоставляемый данным srpm-пакетом:
ACL:
Время сборки: 31 мая 2021, 23:24 ( 147.4 недели назад )
Размер архива: 93.44 Kb
Домашняя страница: http://svn.codehaus.org/mojo/tags/buildnumber-m…
Лицензия: MIT and ASL 2.0
О пакете: Build Number 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, 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.
Текущий майнтейнер: 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.
Список всех майнтейнеров, принимавших участие
в данной и/или предыдущих сборках пакета: Список rpm-пакетов, предоставляемый данным srpm-пакетом:
- buildnumber-maven-plugin
- buildnumber-maven-plugin-javadoc