The starter app parent POM is provided as a convenience to act as the
<parent> for Apache Isis applications.
It builds upon a similar POM provided by the Spring Boot framework, which ensures a consistent set of dependencies, as well as configuring various build plugins.
To use it, just add:
<parent> <groupId>org.apache.isis.app</groupId> <artifactId>isis-app-starter-parent</artifactId> <version>2.0.0-M6</version> (1) </parent>
|1||update as required for new versions of the framework.|
The diagram below shows how the parent POM relates to other POMs:
As the diagram shows, the parent POM inherits two Spring Boot parent POMs: directly from
org.springframework.boot:spring-boot-starter-parent, and transitively inherits from
spring-boot-dependenciesthe second defines numerous
xxx.versionproperties for various third party applications (validated as being compatible with each other by the Spring Boot team), and sets up corresponding
The parent POM also import (using
scope=import, type=pom) each of the "bill of material" POMs provided by Apache Isis framework:
The two core modules most commonly referenced by domain applications are
isis-testing-xxxmodules (fixture scripts, unit test support, integ test support etc)
These all set up
<dependencyManagement>/<dependencies> entries for all of the modules, meaning that there’s only one place to update the version to Apache Isis (the reference to the parent POM).
The parent pom configuresthe Maven surefire plugin to execute multiple times, based on test class suffix. The suffixes are:
Test(unit tests, if any)
this will explicitly exclude any integration tests, though, as defined by …
IntegTest(integ tests, if any)
in 2.0.0-M5 there is a bug in that the
This has been fixed for the next milestone, with a separate execution defined for BDD specs.