Modernize project to Java 17, Thymeleaf 3.1 and remove legacy dependencies#4
Merged
Conversation
Serbroda
commented
Mar 20, 2026
Serbroda
commented
Owner
- Java 8 → 17: Updated compiler target, Maven wrapper (3.9.9), and all plugins
- Thymeleaf 3.0.7 → 3.1.3: Adapted API changes (FragmentExpression.createExecutedFragmentExpression)
- Spring Core removed: Replaced PathMatchingResourcePatternResolver with pure Java NIO (Files.walk, ClassLoader.getResources)
- SLF4J removed: Replaced logging with a custom ComponentDialectException (unchecked) — lets consumers decide how to handle errors
- JUnit 4 → JUnit 5: Migrated all tests to Jupiter API
- CI migrated: Travis CI → GitHub Actions, added Spotless formatting check to verify phase
- Tests expanded: 5 → 22 tests covering nested components, multiple components, named selectors, self-closing tags, manual dialect registration, and ResourcePathFinder
- Java 17 features: Pattern matching instanceof, Set.of()/Map.of(), enhanced try-with-resources, var, precompiled regex Pattern
- Housekeeping: Updated namespace URL, fixed pom.xml description, added license block, contributing guidelines, removed dead code
This was caused by the resource lookup process, which would only work if the files were organized into directories. When packaged into a jar, the "new File(path).listFiles()" would throw the NullPointerException would occur. This addition has the disadvantage of requiring the "org.springframework.spring-core" dependency, in order to be able to use the PathMatchingResourcePatternResolver class.
Fixed issue with "NullPointerException" after building into .jar.
# Conflicts: # pom.xml
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.