marcus
c6379c04f6
- ${revision}-Property im Parent-POM eingeführt; alle Kind-POM-<parent>-Blöcke
verwenden ${revision} statt hartkodierter Version
- flatten-maven-plugin 1.6.0 in <build><plugins> des Parent-POM aktiviert
(resolveCiFriendliesOnly), sodass installierte POMs keine unaufgelösten
${revision}-Referenzen enthalten
- MANIFEST.MF des Shade-JARs enthält Implementation-Version und Implementation-Title
- app.version im Packaging-Modul auf ${revision} umgestellt (war 2.5.0)
- ApplicationVersionProvider: neue Utility-Klasse im Bootstrap-Modul liest
Implementation-Version aus MANIFEST.MF, Fallback "dev" bei ungepacktem Betrieb
- ApplicationVersionProviderTest: prüft Fallback-Verhalten im Testlauf
- .gitignore: .flattened-pom.xml-Dateien ausgeschlossen
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
92 lines
2.7 KiB
XML
92 lines
2.7 KiB
XML
<project xmlns="http://maven.apache.org/POM/4.0.0"
|
|
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
|
|
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 https://maven.apache.org/xsd/maven-4.0.0.xsd">
|
|
<modelVersion>4.0.0</modelVersion>
|
|
<parent>
|
|
<groupId>de.gecheckt</groupId>
|
|
<artifactId>pdf-umbenenner-parent</artifactId>
|
|
<version>${revision}</version>
|
|
</parent>
|
|
<artifactId>pdf-umbenenner-coverage</artifactId>
|
|
<packaging>pom</packaging>
|
|
|
|
<dependencies>
|
|
<dependency>
|
|
<groupId>de.gecheckt</groupId>
|
|
<artifactId>pdf-umbenenner-domain</artifactId>
|
|
<version>${project.version}</version>
|
|
</dependency>
|
|
<dependency>
|
|
<groupId>de.gecheckt</groupId>
|
|
<artifactId>pdf-umbenenner-application</artifactId>
|
|
<version>${project.version}</version>
|
|
</dependency>
|
|
<dependency>
|
|
<groupId>de.gecheckt</groupId>
|
|
<artifactId>pdf-umbenenner-adapter-in-cli</artifactId>
|
|
<version>${project.version}</version>
|
|
</dependency>
|
|
<dependency>
|
|
<groupId>de.gecheckt</groupId>
|
|
<artifactId>pdf-umbenenner-adapter-out</artifactId>
|
|
<version>${project.version}</version>
|
|
</dependency>
|
|
<dependency>
|
|
<groupId>de.gecheckt</groupId>
|
|
<artifactId>pdf-umbenenner-bootstrap</artifactId>
|
|
<version>${project.version}</version>
|
|
</dependency>
|
|
</dependencies>
|
|
|
|
<build>
|
|
<plugins>
|
|
<plugin>
|
|
<groupId>org.jacoco</groupId>
|
|
<artifactId>jacoco-maven-plugin</artifactId>
|
|
<executions>
|
|
<execution>
|
|
<id>jacoco-report-aggregate</id>
|
|
<phase>verify</phase>
|
|
<goals>
|
|
<goal>report-aggregate</goal>
|
|
</goals>
|
|
</execution>
|
|
</executions>
|
|
</plugin>
|
|
|
|
<plugin>
|
|
<groupId>org.pitest</groupId>
|
|
<artifactId>pitest-maven</artifactId>
|
|
<executions>
|
|
<execution>
|
|
<id>pitest</id>
|
|
<phase>verify</phase>
|
|
<goals>
|
|
<goal>mutationCoverage</goal>
|
|
</goals>
|
|
<configuration>
|
|
<skip>true</skip>
|
|
</configuration>
|
|
</execution>
|
|
<execution>
|
|
<id>pitest-report-aggregate</id>
|
|
<phase>verify</phase>
|
|
<goals>
|
|
<goal>report-aggregate</goal>
|
|
</goals>
|
|
<configuration>
|
|
<!-- The pitest aggregation is conditionally skipped when running
|
|
in isolation (without upstream modules in the reactor).
|
|
This module is designed to be run as part of the full multi-module build.
|
|
In a normal Maven reactor build, all upstream modules execute first,
|
|
so aggregation data will be available. If this module is run alone
|
|
(e.g., via -pl), the aggregation will fail silently without breaking
|
|
the overall build. -->
|
|
<skip>${pitest.aggregate.skip}</skip>
|
|
</configuration>
|
|
</execution>
|
|
</executions>
|
|
</plugin>
|
|
</plugins>
|
|
</build>
|
|
</project> |