Nova Ordis Utilities Version Metadata Handling: Difference between revisions
Jump to navigation
Jump to search
| Line 11: | Line 11: | ||
In case the metadata file is not found, the both methods log the condition using SLF4J warn() and return null. | In case the metadata file is not found, the both methods log the condition using SLF4J warn() and return null. | ||
In order to insure that the artifacts are built to contain version metadata, follow [[]] below. | In order to insure that the artifacts are built to contain version metadata, follow the instructions provided in the "[[#Build_Infrastructure_Configuration|Build Infrastructure Configuration]]" section, below. | ||
=Code= | =Code= | ||
Revision as of 18:02, 16 November 2016
Internal
Overview
The mechanism relies on the presence of a "VERSION" metadata file in the application's classpath.
VersionUtilities.getVersion() and VersionUtilities.getReleaseDate() can be used as top-level API to locate, process and display the metadata.
In case the metadata file is not found, the both methods log the condition using SLF4J warn() and return null.
In order to insure that the artifacts are built to contain version metadata, follow the instructions provided in the "Build Infrastructure Configuration" section, below.