- Allow configurations to be ignored via Jarek Lewandowski/jotel
- Handle maven repos that require credentials via Tomasz Jędrzejewski zyxist and Stephan Pauxberger/pauxus
- BUGFIX remove possible infinite loop on creation of a bom
- BUGFIX handle boms with profiles and other things by passing in System.properties
- Add a
strictMode
flag - this will fail builds that have omitted versions that are not found in one of the recommendation sources
- Begin using
nebula.dependency-base
plugin.- Gives us
dependencyInsightEnhanced
task to show what was recommended instead ofselected by rule
in reasons
- Gives us
- Remove
getProjectConfiguration
deprecation warning on Gradle 3.4
- Close
InputStream
for properties and file based providers to avoid file locking issues on Windows
- BREAKING: Change to
ConflictResolvedStrategy
. First order recommendations will not auto-win, they will go through conflict resolution.
- Add
nebulaRecommenderBom
configuration as an alternative to the extension methodmavenBom
- BUGFIX handle recommendations across a multiproject where subproject B depends on A which has a dependency it needs to pick up from recommendations
- Handle the gradle-dependency-lock V4 format
- 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 listingOverrideTransitives
- If a recommendation conflicts with a transitive, pick the transitive
- Fixed bug where GString inputs to Maven BOM and Ivy module attribute were not appended with the file type
- Add a dependency on maven-module-builder which Gradle now shades
- Upgrade to Gradle 2.7