-
Changes in Version 3.6.2 (2021-01-22)
Changes in Version 3.5.0 (2020-06-04)
Changes in Version 3.4.2 (2020-03-26)
Changes in Version 3.3.1 (2019-08-22)
Changes in Version 3.3.0 (2019-01-09)
Changes in Version 3.2.1 (2018-12-21)
Changes in Version 3.2.0 (2018-08-27)
Changes in Version 3.1.1 (2018-06-29)
Changes in Version 3.1.0 (2018-03-27)
Changes in Version 3.0.0 (2018-02-20)
Build Systems
Dependency Management
Each release of tapir defines a list of dependencies. In practice, you do not need to provide a version for any of these dependencies in your build configuration as tapir is managing this for you. When you upgrade tapir itself, these dependencies will be upgraded as well in a consistent way.
We recommend the usage of Maven. Gradle might work as well, but is not officially supported.
Maven users can use the tapir-starter-module to obtain sensible defaults. The project provides the following features:
- Java 1.8 as default compiler level
- UTF-8 source encoding
- A Dependency Management section, allowing you to omit <version> tags for common dependencies, inherited by tapir-dependencies POM
- A Dependency section containing some must-have dependencies
- The Maven filtering is changed to use
@..@
placeholders
Inheriting the Starter Parent
To configure your project to inherit from the tapir-starter-module simply set the parent:
<!-- Inherit defaults from tapir -->
<parent>
<groupId>de.bmiag.tapir</groupId>
<artifactId>tapir-starter-module</artifactId>
<version>3.6.2</version>
</parent>
With that setup, you can also override individual dependencies by overriding a property in your own project. For instance, to upgrade to another Selenium version you would add the following to your pom.xml.
<properties>
<selenium.version>3.4.0</selenium.version>
</properties>
Using tapir Without the Parent POM
If you don’t want to use the tapir-starter-module, you can still keep the benefit of the dependency management (but not the plugin management) by using a dependency with the import scope:
<dependencyManagement>
<dependencies>
<dependency>
<!-- Import dependency management from tapir -->
<groupId>de.bmiag.tapir</groupId>
<artifactId>tapir-dependencies</artifactId>
<version>3.6.2</version>
<type>pom</type>
<scope>import</scope>
</dependency>
</dependencies>
</dependencyManagement>
That setup does not allow you to override individual dependencies using a property as explained above.
Additional Starters
There a more specialized starters provided by tapir. Those starters are explained below.
tapir-starter-selenium-allure
If you would like to use tapir’s Selenium implementation and the Allure report capabilities you might want to use tapir-starter-selenium-allure. The project provides the following features:
- Inherits from tapir-starter-module
- Configures the following Maven Plugins:
- maven-surefire-plugin
- maven-failsafe-plugin
- allure-maven-plugin
- jetty-maven-plugin
- Configures the following Reporting Plugins:
- allure-maven-plugin
- Specifies compile-time and runtime dependencies which are needed for Selenium and Allure usage
- Previous
- Next