Closed ceefour closed 9 years ago
Weird. It should already be excluded https://github.com/spring-projects/spring-boot/blob/v1.2.0.RELEASE/spring-boot-starters/spring-boot-starter-remote-shell/pom.xml#L91-L96.
Are you actually seeing it appear in your final jar?
Could this be due to Gradle's different handling of exclusions? That dependency tree output looks like Gradle's
Indeed I'm using Gradle. But I haven't confirmed if this is indeed Gradle's intended behavior or a particular bug.
If it's Gradle's intended behavior then surely my project would have more wrong dependencies that just this one...
On Wed, Dec 31, 2014, 14:34 Andy Wilkinson notifications@github.com wrote:
Could this be due to Gradle's different handling of exclusions? That dependency tree output looks like Gradle's
— Reply to this email directly or view it on GitHub https://github.com/spring-projects/spring-boot/issues/2257#issuecomment-68428159 .
Sadly, Gradle handle's exclusions differently to Maven even when it's processing a Maven pom.
In this case groovy-all
is pulled in via org.crashub:crash.shell
where we've excluded it. This is enough to prevent Maven from pulling in groovy-all
when you depend on the remote shell starter. org.crashub:crash.shell
is also pulled in as a transitive dependency of a number of other dependencies and Gradle requires each of these to also exclude groovy-all
for it to actually be excluded.
The long-term fix for this is #2133.
Since
spring-boot-starter-remote-shell
already depends on groovy 2.3.8, shouldn't it exclude groovy-all 1.8.9 ?