Browse Source
It seems that publishing a Gradle platform as a Maven POM writes all dependencies with their scope information by default. We don't want that when publishing the Spring Framework BOM, as it forces the scope on projects depending on the BOM, unless they've specified the scope when they added the dependency to their build. Typically, developers could get spring-test as a compile dependency without this change. This commit removes the scope information from the published BOM. Fixes gh-23660pull/23772/head
Brian Clozel
5 years ago
1 changed files with 6 additions and 0 deletions
Loading…
Reference in new issue