Repository navigation
A file whose name matches the patterns of several layouts no longer blocks every run when one of those layouts has already processed it. Without overlapping patterns, 0.6.0 behaves like 0.5.0. No API changes.
Changed
-
Ambiguous files that were already processed are ignored. A listed file matching the patterns of several root layouts used to fail the whole run with
AMBIGUOUS_LAYOUT, even if it was old and already imported. Now it is ignored when any of those layouts already covers it:- its timestamp is not after that layout's watermark (with
duplicateProtection.watermark), or - the
alreadyProcessedpredicate reports it.
It is logged at DEBUG. A file none of them covers still fails the run with
AMBIGUOUS_LAYOUT, and a file matching several layouts is never assigned to one of them. Old files left on a server no longer block a definition that gains an overlapping pattern. - its timestamp is not after that layout's watermark (with
Fixed
- With a name matching several patterns, each layout's watermark is compared with the timestamp extracted by its own pattern, not by the last pattern that matched.
Artifacts
| Artifact | |
|---|---|
io.github.tie-integration-engine:tie-core:0.6.0 |
The library |
io.github.tie-integration-engine:tie-jexl:0.6.0 |
Optional programmable fields with Apache Commons JEXL |
io.github.tie-integration-engine:tie-spring-boot-starter:0.6.0 |
Optional Spring Boot 4 auto-configuration |
Available on Maven Central:
<dependency>
<groupId>io.github.tie-integration-engine</groupId>
<artifactId>tie-core</artifactId>
<version>0.6.0</version>
</dependency>The jars, with their sources and javadoc, are attached below. Requires Java 25.
Documentation
- README and CHANGELOG.
- Full diff: v0.5.0...v0.6.0.
- Modules: tie-core, tie-jexl and tie-spring-boot-starter.