spring-projects / spring-projects/spring-boot
Support Gradle's isolated projects feature
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 81.5k
- Forks
- 42.7k
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 65
Description
https://docs.gradle.org/current/userguide/isolated_projects.html
Experimenting with the feature today shows that our ResolvableDependencies, used both for layered jars and for identifying GraalVM metadata , isn't compatible. https://github.com/gradle/gradle/issues/31973 is tracking a change in Gradle will hopefully improve the situation.
Related, https://github.com/spring-gradle-plugins/dependency-management-plugin/issues/380 is tracking a similar enhancement to the dependency management plugin. In addition to being blocked on the above Gradle issue, it's also blocked on https://github.com/gradle/gradle/issues/25179.
Contributor guide
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
Start with the Gradle isolated projects documentation and inspect the uses of ResolvableDependencies for layered jars and GraalVM metadata. Review the linked Gradle issues 31973 and 25179 and dependency-management-plugin issue 380 before changing Spring Boot. Done means isolated projects support is compatible with these uses, but the payload indicates external blockers remain.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100