vaadin / vaadin/flow-spring-examples
PiT 25.1: commons-io dependency missing version, fails with Spring Boot 4.x
Open
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 64
- Forks
- 41
- Avg merge
- 51m
- Merged PRs (30d)
- 2
Description
Description
The commons-io dependency in pom.xml (line 125) has no explicit version:
<dependency>
<groupId>commons-io</groupId>
<artifactId>commons-io</artifactId>
<scope>compile</scope>
</dependency>
With Vaadin 25.0.x (Spring Boot 3.x), the version was resolved transitively from the Spring Boot BOM. With Vaadin 25.1.x (Spring Boot 4.x), commons-io is no longer managed by the Spring Boot BOM, so Maven fails:
[ERROR] 'dependencies.dependency.version' for commons-io:commons-io:jar is missing. @ line 125, column 21
Fix
Add explicit version:
<dependency>
<groupId>commons-io</groupId>
<artifactId>commons-io</artifactId>
<version>2.21.0</version>
<scope>compile</scope>
</dependency>
Environment
- Vaadin 25.1.0-beta1 (Spring Boot 4.0.3)
- Passes with Vaadin 25.0.6 (Spring Boot 3.x)
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Open pom.xml and inspect the commons-io dependency around line 125. Reproduce the Maven failure with the Spring Boot 4.x/Vaadin 25.1.x setup, then verify that the dependency has an explicit version and Maven no longer reports a missing-version error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring-boot
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 48/100