-
Notifications
You must be signed in to change notification settings - Fork 9
Supported Files
Version Tiger supports the following file types for looking at and updating version numbers:
Each project is currently required to have a pom.xml file. The Version Tiger may update the project and the parent version and also considers the dependencies and dependencyManagement section.
If a maven project inherits its version from the parent, the Version Tiger won't ever update the project version but it will update the parent dependency (and the version in Manifest.MF, etc...) if you re-version the parent project.
In the command line tool there is a command for updating maven properties. The Version Tiger can't detect versions but it will just update the properties as you define in the command.
You may define a property versionTigerFiles
in order to register more files that contain version numbers. Currently, we only support the Apache Karaf feature files. The property takes a comma separated list of files prefixed with its file type (e.g. karaf:
), e.g.:
<properties>
<versionTigerFiles>karaf:subFolder/feature.xml, karaf:feature.xml</versionTigerFiles>
</properties>
If the maven packaging type is eclipse-plugin
, Version Tiger will also update the MANIFEST.MF
file. It updates Bundle-Version
, Require-Bundle
and Fragment-Host
headers.
For the maven packaging type eclipse-feature
, Version Tiger can update its own feature version and update dependencies in plugins and includes.
For the eclipse-repository
packaging type, Version Tiger will look at all .product
files in the root and updates the maven project and the feature and plugins dependencies. The category.xml
file is also supported for updating feature dependencies.
In the obsolete packaging type eclipse-application
, the product file must correspond to the project id. The Version Tiger supports updating the product version and product feature dependencies.
Version Tiger supports updating site features in the site.xml
file for the packaging type eclipse-updatesite
.
The Version Tiger can also update maven dependencies in feature files from Apache Karaf. (for any bundle which uses the mvn:
prefix).
As there is no convention for the feature.xml
location in a project, you'll have to register the file using the prefix karaf:
in the maven project. See above in Maven Projects how to register additional files.