Optional dependencies are missing from the poms of the latest 5.0 snapshots [SPR-15167]

[spring-projects-issues]

Andy Wilkinson opened SPR-15167 and commented

It appears to be related to starting to use the dependency management plugin to import Reactor's bom. I'm guessing there's a clash between it and whatever was adding the optional dependencies to the pom (the propdeps plugin?).

I'll investigate and hopefully open a PR once I've figured out what the root cause is and how to fix it.

---

Affects: 5.0 M5

Referenced from: commits b1fed6f, 6fe7b17

[spring-projects-issues]

Andy Wilkinson commented

Pull request: #1301

[spring-projects-issues]

Brian Clozel commented

Thanks Andy Wilkinson, I'll merge this right away.

Quick question - now that we're using Gradle 3.3, should we use compileOnly and drop the propdeps plugin?

[spring-projects-issues]

Brian Clozel commented

This isn't fixed yet. Since SPR-PUB-4411, we're getting the following:

FAILURE: Build failed with an exception.

* What went wrong:
A problem was found with the configuration of task ':spring-build-src:artifactoryPublish'.
> File '/opt/bamboo-home/xml-data/build-dir/SPR-PUB-JOB1/buildSrc/build/poms/pom-default.xml' specified for property 'mavenDescriptor' does not exist.

Note: "propdeps-maven" is already applied by "gradle/publish-maven.gradle", which is itself applied on all projects but "spring-build-src".

[spring-projects-issues]

Brian Clozel commented

This second PR fixed the remaining issues.

Thanks Andy Wilkinson!