The buildnumber-maven-plugin provides a build number, too. While the buildmetadata-maven-plugin aims to make it easy to include any meta data within the generated artifact, the buildnumber-maven-plugin focuses on handling build numbers. If the way the buildmetadata-maven-plugin deals with build numbers does not meet your needs, we recommend to have a look at the buildnumber-maven-pluginNo, we do not generate a consecutive build number. The problem is that this number has to be stored somewhere. In previous versions of this plugin this number was stored in the POM and then has to be given to the SCM. But changing the POM by each build seems somewhat odd. This information is relevant to the artifact created, but not to the source. | hide | Doctype | faq | hide |
---|
Name | I'm looking for a unique build number generated to identify the artifact created. Is a build number part of the meta data generated by this plugin? |
---|
| |
| Audience | Name List |
---|
doctype | role |
---|
render-no-hits-as-blank | true |
---|
property | Audience |
---|
|
|
---|
|
| Subject | Name List |
---|
doctype | subject |
---|
property | Subject |
---|
|
|
---|
|
| Categories | Name List |
---|
doctype | category |
---|
property | Categories |
---|
|
|
---|
| |
| Iteration | | hide |
---|
Sort Key | | hide |
---|
|