nebula-dependency-recommender-plugin icon indicating copy to clipboard operation
nebula-dependency-recommender-plugin copied to clipboard

Leave off version numbers in your dependencies section and have versions recommended by several possible sources.

Results 20 nebula-dependency-recommender-plugin issues
Sort by recently updated
recently updated
newest added

Make use of the double-check pattern to initialize the recommendation HashMap.

Given the current documentation of the README that this plug-in is deprecated in favor of the Gradle BOM feature, it would be helpful to have an "example migration" provided -...

The docs indicate that: > If more than one recommender defines a recommended version for a module, the last recommender specified will win. However, the `mavenBomProvider` is always added first...

Steps to reproduce: create `build.gradle`: ``` buildscript { repositories { maven { url 'https://plugins.gradle.org/m2/' } } dependencies { classpath 'com.netflix.nebula:nebula-dependency-recommender:4.0.2' } } repositories { mavenCentral() } apply plugin: 'java' apply...

bug

Hi! The recommendation plugin traverses up the project hierarchy to find a suitable recommendation in one of the parent projects, which is a good feature. But as soon as the...

Hi, I'm using plugin version 3.6.2. It seems the current behavior of maven bom provider does not prioritize local properties when they are defined in the pom alwell. I'm not...

I primarily use nebula-dependency-recommender on multi-project repositories and have found the properties file provider to be really helpful for consolidating versions in a single place. I've recently been exploring using...

Assume we have an external library with transitive dependecy: ``` external:lib:2.0 \ -- external:lib-trans:1.2 ``` In the past `lib-trans` v1.0 had a major bug and was updated to v1.1, and...

[This commit](https://github.com/nebula-plugins/nebula-dependency-recommender-plugin/commit/9d5a56c46eeeff71117f0af42a8c7cf976067e50#diff-f6d49aabb8efe40a937ed8597b0b28a4R35) added support for traversing project dependencies. However, the `ProjectDependency.getProjectConfiguration()` call assumes that the downstream project has already been notified of pre-resolution, and evaluated itself if necessary. This is...

bug

We would like to be able easily to pass through other recommendations BOM, something like: ``` dependencies { recommendation 'netflix.grpc:netflix-grpc-recommendations:latest.release@pom' } ``` where `netflix.grpc:netflix-grpc-recommendations:latest.release@pom` is the other recommendations BOM to...