nebula-plugins/nebula-dependency-recommender-plugin issues and pull requests

#122 - JDK 17 tests

Pull Request - State: closed - Opened by rpalcolea almost 3 years ago

#121 - Update assertion to support Gradle 7 and 6

Pull Request - State: closed - Opened by chali over 3 years ago

#120 - Gradle 7.0 compatibility

Pull Request - State: closed - Opened by chali over 3 years ago - 1 comment

#119 - Gradle 7.0 compatibility

Pull Request - State: closed - Opened by chali over 3 years ago - 1 comment

#118 - Update build badge to use travis-ci.com

Pull Request - State: closed - Opened by emccallum almost 4 years ago - 1 comment

#117 - Extend application of gradle platforms to all annotationProcessor configurations

Pull Request - State: closed - Opened by chali about 4 years ago

#116 - Core platform applied through recommender plugin (when using feature flag) are not propagated into consumable apiElements and runtimeElements. It means they are not published as dependendencies

Pull Request - State: closed - Opened by chali about 4 years ago - 1 comment

#115 - When version is found through recursion find also reasons of recommendation

Pull Request - State: closed - Opened by chali over 4 years ago - 2 comments

#114 - Remove extending internal Gradle class and replace it with delegation…

Pull Request - State: closed - Opened by chali almost 5 years ago - 2 comments

#113 - Use implementation configuration for tests

Pull Request - State: closed - Opened by rpalcolea almost 5 years ago - 1 comment

#112 - make sure we do not apply recommendations for provided versions by Gradle

Pull Request - State: closed - Opened by rpalcolea almost 5 years ago - 2 comments

#111 - Mark copied configurations as non-resolvable so that we do not lock copies of BOM configurations

Pull Request - State: closed - Opened by OdysseusLives about 5 years ago - 2 comments

#110 - introduce static compilation for groovy artifacts

Pull Request - State: closed - Opened by rpalcolea about 5 years ago - 1 comment

#109 - Use findByType instead if getByType

Pull Request - State: closed - Opened by rpalcolea about 5 years ago - 2 comments

#108 - Add compatibility with Gradle 6

Pull Request - State: closed - Opened by chali about 5 years ago - 1 comment

#107 - Break infinite loop with Gradle 5.6 when adding configuraiton for core bom support

Pull Request - State: closed - Opened by chali about 5 years ago - 1 comment

#106 - Make getRecommendedVersionRecursive public for use in another plugin

Pull Request - State: closed - Opened by OdysseusLives over 5 years ago - 1 comment

#105 - Maven BOMs do not respect provider specification order

Issue - State: open - Opened by henryptung over 5 years ago

#104 - make sure we ignore configurations for spotbugs and findbugs

Pull Request - State: closed - Opened by rpalcolea over 5 years ago - 1 comment

#103 - support for configuration prefixes in exclusions

Pull Request - State: closed - Opened by rpalcolea over 5 years ago - 1 comment

#102 - Add Example(s) of Nebula -> Gradle Feature Migration

Issue - State: open - Opened by romeara over 5 years ago - 5 comments

#101 - Reduce logging of coreBomSupport enabled notification

Pull Request - State: closed - Opened by chali over 5 years ago - 1 comment

#100 - Add ability to resolve and read BOMs with Gradle core based implementation. Useful for publishing custom BOMs

Pull Request - State: closed - Opened by chali over 5 years ago - 1 comment

#99 - Allow to use mavenBom with core recommender as strict platforms

Pull Request - State: closed - Opened by chali over 5 years ago - 1 comment

#98 - Error when applying the plugin

Issue - State: closed - Opened by gmariotti over 5 years ago - 6 comments

#97 - Exclude tools configurations from applying recommendatation from bom

Pull Request - State: closed - Opened by chali almost 6 years ago - 1 comment

#96 - Modify integration tests to use standardError for runTasksWithFailure - required by gradle 5.1

Pull Request - State: closed - Opened by rpalcolea almost 6 years ago

#95 - Only unresolved configurations will receive recommendation from BOM

Pull Request - State: closed - Opened by chali almost 6 years ago - 1 comment

#94 - Exclude protoloc configuration from recommendations, configuration is add by protobuf plugin and is resolved sooner then recommendation is provided

Pull Request - State: closed - Opened by chali almost 6 years ago - 1 comment

#93 - Travis openjdk8

Pull Request - State: closed - Opened by rpalcolea almost 6 years ago

#92 - Fix nebula recommender bom support

Pull Request - State: closed - Opened by rpalcolea almost 6 years ago - 1 comment

#91 - Use explicit gradle platform for experimental core bom support

Pull Request - State: closed - Opened by chali about 6 years ago - 1 comment

#90 - Upgrade plugin-plugin to 8.0.0

Pull Request - State: closed - Opened by rpalcolea about 6 years ago - 1 comment

#89 - Update exclusions from recommendations

Pull Request - State: closed - Opened by sghill about 6 years ago

#88 - Return back to eagerly resolve all recommendation

Pull Request - State: closed - Opened by chali about 6 years ago - 1 comment

#87 - Gradle 5.0 Compatibility

Pull Request - State: closed - Opened by sghill about 6 years ago - 1 comment

#86 - Exclude additional configurations for core publishing

Pull Request - State: closed - Opened by chali about 6 years ago - 1 comment

#85 - Feature flag implementation to delegate to IMPROVED_POM_SUPPORT

Pull Request - State: closed - Opened by sghill about 6 years ago - 1 comment

#84 - Core gradle insight

Pull Request - State: closed - Opened by OdysseusLives about 6 years ago - 1 comment

#83 - Updates to make plugin compatible with Gradle 4.8

Pull Request - State: closed - Opened by chali over 6 years ago - 1 comment

#82 - Updates to make plugin compatible with Gradle 4.8

Pull Request - State: closed - Opened by chali over 6 years ago - 1 comment

#81 - Migrate to Gradle 4.6

Pull Request - State: closed - Opened by chali over 6 years ago - 1 comment

#80 - Circular

Pull Request - State: closed - Opened by rspieldenner over 6 years ago - 1 comment

#79 - Issue #78 Fixed thread safety for multiproject builds with --parallel

Pull Request - State: open - Opened by cbue almost 7 years ago - 2 comments

#78 - Lazy initialization of recommendation providers is not thread-safe for multiproject builds with --parallel

Issue - State: open - Opened by cbue almost 7 years ago

#77 - Gradle4dot4

Pull Request - State: closed - Opened by rspieldenner almost 7 years ago - 1 comment

#76 - ConcurrentModificationException in FuzzyVersionResolver

Issue - State: closed - Opened by mnazbro almost 7 years ago

#75 - Add thread safety for glob initialization.

Pull Request - State: closed - Opened by billbindi almost 7 years ago - 4 comments

#74 - Reduce logging level to debug for recommendations

Pull Request - State: closed - Opened by justinuang almost 7 years ago - 3 comments

#73 - Demote recommending message to debug - Reduce noise in output

Pull Request - State: closed - Opened by danhyun almost 7 years ago - 2 comments

#72 - Add test for multiple boms

Pull Request - State: closed - Opened by rspieldenner almost 7 years ago - 1 comment

#71 - using dependencyLock and propertiesFile providers together

Issue - State: open - Opened by gracew about 7 years ago - 1 comment

#70 - Dependencies aren't recommended for buildscript dependencies

Issue - State: closed - Opened by dinomite about 7 years ago - 2 comments

#69 - add note re: root project applictaion

Pull Request - State: closed - Opened by jmcampanini about 7 years ago - 3 comments

#68 - InvalidUserDataException exception when getRecommendedVersion is used with a copy action

Issue - State: closed - Opened by vbuell about 7 years ago - 2 comments

#67 - Support EOL comments

Pull Request - State: closed - Opened by ash211 about 7 years ago - 3 comments

#66 - Support trailing line comments in properties files

Issue - State: closed - Opened by ash211 about 7 years ago - 1 comment

#65 - Better generation

Pull Request - State: closed - Opened by rspieldenner about 7 years ago - 1 comment

#64 - Ability to omit mavenBom version if it's provided elsewhere

Issue - State: closed - Opened by szunami over 7 years ago - 1 comment

#63 - Resolve errors with copied configuration [4.2.1, Gradle 4.0]

Issue - State: closed - Opened by dansanduleac over 7 years ago - 1 comment

#62 - Recreation of PR #39

Pull Request - State: closed - Opened by pauxus over 7 years ago

#61 - pass in System.properties to MavenProvider, fixes #45

Pull Request - State: closed - Opened by rspieldenner over 7 years ago

#60 - Support Merging Recommendations instead of "Last one wins"

Issue - State: closed - Opened by twicksell over 7 years ago - 1 comment

#59 - Ability to exclude certain gradle configurations, resolves #58

Pull Request - State: closed - Opened by jotel over 7 years ago - 1 comment

#58 - Provide ability to exclude certain gradle configurations

Issue - State: closed - Opened by jotel over 7 years ago - 1 comment

#57 - Add a note on how to generate valid POM files

Pull Request - State: closed - Opened by romeara over 7 years ago

#56 - Provide errors for misconfigured version.props file

Issue - State: closed - Opened by amrasarfeiniel over 7 years ago - 2 comments

#55 - Fail on missing recommendation

Pull Request - State: closed - Opened by rspieldenner over 7 years ago

#54 - Strategy for transitive conflicts (or minimal version)?

Issue - State: open - Opened by slavashvets over 7 years ago - 1 comment

#53 - extra "/" when downloading parent poms via mavenCentral()

Issue - State: closed - Opened by gregallen over 7 years ago - 1 comment

#52 - Add info for newer version of Gradle

Pull Request - State: closed - Opened by The-Alchemist over 7 years ago

#51 - nebula dependency recommender not compatible with spring io dependency management

Issue - State: closed - Opened by wilkystorm over 7 years ago - 2 comments

#50 - Spring Cloud BOMs are not applied correctly

Issue - State: closed - Opened by dengayevskiy over 7 years ago - 4 comments
Labels: bug

#49 - Substituted dependencies have version replaced by recommendation

Issue - State: closed - Opened by DanielThomas over 7 years ago

#48 - Honour Maven excludes in dependency-recommender

Issue - State: closed - Opened by uschi2000 over 7 years ago - 3 comments

#47 - Use nebula.dependency-base

Pull Request - State: closed - Opened by rspieldenner over 7 years ago

#46 - Fix README BOM example

Pull Request - State: closed - Opened by markelliot over 7 years ago

#45 - Maven BOM with profile fails to find `java.version`

Issue - State: closed - Opened by stealthcode over 7 years ago - 4 comments
Labels: bug

#44 - Update version in README to latest released 4.0.2

Pull Request - State: closed - Opened by Godin over 7 years ago - 1 comment

#43 - "mavenBom file: 'pom.xml'" causes error "Module may not be null"

Issue - State: open - Opened by Godin over 7 years ago - 9 comments
Labels: bug

#42 - Add specificity ordering to glob matching

Pull Request - State: closed - Opened by henryptung over 7 years ago - 1 comment

#41 - Cannot generate BOM file

Issue - State: closed - Opened by viktornordling over 7 years ago - 2 comments

#39 - Fixes for issues #37 and #38

Pull Request - State: closed - Opened by zyxist over 7 years ago - 1 comment

#38 - Maven BOM provider fails, if Maven repository requires authentication

Issue - State: closed - Opened by zyxist over 7 years ago - 1 comment

#37 - Maven BOM provider uses Maven API incorrectly, producing meaningless exceptions if dependency resolution fails

Issue - State: closed - Opened by zyxist over 7 years ago - 1 comment

#35 - Update README example with new publishing extension 'nebulaDependency…

Pull Request - State: closed - Opened by billkoch over 7 years ago - 1 comment

#33 - Dependency recommender incompatible with configure-on-demand

Issue - State: open - Opened by henryptung over 7 years ago
Labels: bug

#32 - Recommendation does not work with composite builds

Issue - State: closed - Opened by vitjouda over 7 years ago - 6 comments
Labels: bug

#27 - FuzzyVersionResolver: clearly defining and improving syntax

Issue - State: closed - Opened by henryptung almost 8 years ago - 2 comments

#26 - Local properties are not prioritized in BOM

Issue - State: open - Opened by joke almost 8 years ago - 1 comment

#25 - Move bom lookup to a gradle configuration

Issue - State: closed - Opened by rspieldenner almost 8 years ago

#22 - Slight error in documentation

Issue - State: closed - Opened by dbahlbeck about 8 years ago - 1 comment

#21 - Ignore buildscript/classpath configuration

Issue - State: closed - Opened by markelliot about 8 years ago

#14 - Recommender-plugin breaks project dependencies

Issue - State: closed - Opened by remmeier over 8 years ago - 3 comments

#12 - Project dependencies may introduce inconsistent version recommendations

Issue - State: closed - Opened by uschi2000 over 8 years ago - 2 comments

#11 - Changed the name of the extension used for BOM generation

Pull Request - State: closed - Opened by adrianjgeorge over 8 years ago - 6 comments

#10 - Incompatible with Spring Boot plugin

Issue - State: closed - Opened by adrianjgeorge over 8 years ago - 6 comments

#9 - Gradle generated pom files when nebula recommender is used are missing dependency versions

Issue - State: closed - Opened by CesarIzzat over 8 years ago - 2 comments

#8 - when using nebula, both `artifactoryPublish` and `publishRecommenderPublicationToBomRepository` publish the same pom file

Issue - State: closed - Opened by noel-yap over 8 years ago

#7 - java plugin required when using recommender plugin

Issue - State: closed - Opened by noel-yap over 8 years ago - 2 comments

GitHub / nebula-plugins/nebula-dependency-recommender-plugin issues and pull requests