v3.7.0

• Add nebulaRecommenderBom configuration for pom based boms
• Shift mavenBom calls in the plugin extension to add the bom to the configuration

v3.6.3

• BUGFIX handle recommendations across a multiproject where subproject B depends on A which has a dependency it needs to pick up from recommendations

v3.6.2

Evaluate dependencies for BOM publishing only when withXml is called, preventing dependency resolution when the publications container is evaluated

v3.6.1

Don't run recommendations providers unless a recommendation will be needed. Avoids interactions with publishing due to getProperties call on the project (@ netflix.nebula.dependency.recommender.provider.MavenBomRecommendationProvider$ProjectPropertiesModelInterpolator.createValueSources(MavenBomRecommendationProvider.java:137)

v3.6.0

Renames the dependencyManagement publishing extension to nebulaDependencyManagement to avoid conflicts with Spring dependency management plugin

v3.5.0

Apply all plugin logic inside a single incoming.beforeResolve block so ordering is predictable when interacting with other plugins

v3.4.0

Change default recommendation strategy to ConflictResolved

v3.3.0

No longer need java plugin applied to use recommendation source

v3.2.0

• Handle gradle-dependency-lock V4 format

v3.1.0

• Offer two strategies for how recommendations interact with transitive dependencies:
  • ConflictResolved - If there is no first order recommend-able dependency, a transitive will conflict resolve with dependencies in the recommendations listing
  • OverrideTransitives - If a recommendation conflicts with a transitive, pick the transitive