Ecosyste.ms: Issues
An open API service for providing issue and pull request metadata for open source projects.
GitHub / spring-gradle-plugins/dependency-management-plugin issues and pull requests
#301 - Fix deprecation warnings in the CI pipeline
Issue -
State: closed - Opened by wilkinsona almost 4 years ago
Labels: type: task
#300 - Remove Bintray from CI release pipeline
Issue -
State: closed - Opened by wilkinsona almost 4 years ago
- 1 comment
Labels: type: task
#299 - Rename default branch to main
Issue -
State: closed - Opened by wilkinsona almost 4 years ago
Labels: type: task
#298 - Exclusions from Maven BOMs not applied under specific conditions
Issue -
State: closed - Opened by GFriedrich almost 4 years ago
- 3 comments
Labels: status: declined
#297 - Support for Gradle Configuration Cache
Issue -
State: closed - Opened by Fabian-K almost 4 years ago
- 9 comments
Labels: status: invalid, for: external-project
#296 - Wrong configuration assigned to dependency 'org.moduliths:moduliths-core' when used with the `dependency-management-plugin`
Issue -
State: closed - Opened by odiolog almost 4 years ago
- 4 comments
Labels: status: invalid
#295 - Remove duplicate String-based dependency management declaration from Map-based Kotlin example
Pull Request -
State: closed - Opened by jongmin92 about 4 years ago
- 1 comment
Labels: type: documentation
#294 - Update CI to use Concourse's registry-image resource
Issue -
State: closed - Opened by wilkinsona about 4 years ago
Labels: type: task
#293 - NPE thrown from Exclusion.hashCode when processing an exclusion with no <groupId> or no <artifactId>
Issue -
State: closed - Opened by philwebb about 4 years ago
- 5 comments
Labels: type: regression
#292 - Document lack of support for classifiers
Issue -
State: open - Opened by mjustin about 4 years ago
Labels: type: documentation
#291 - click download sources failed in idea
Issue -
State: closed - Opened by wang007 about 4 years ago
- 3 comments
Labels: status: invalid
#289 - High CPU usage when identifying local projects in large multi-project builds
Pull Request -
State: closed - Opened by kazuki-ma about 4 years ago
- 2 comments
Labels: type: bug
#288 - Applying Spring Boot Gradle plugin to large scale multi project slow down IntelliJ reload.
Issue -
State: closed - Opened by kazuki-ma about 4 years ago
- 4 comments
Labels: status: declined
#287 - Multiple nested BOM imports, the last one does not win
Issue -
State: closed - Opened by edudar about 4 years ago
- 3 comments
Labels: status: invalid
#286 - after using `maven-publish` to package and release and introduced to other projects, the version is lost
Issue -
State: closed - Opened by halower about 4 years ago
- 7 comments
Labels: status: invalid
#285 - NPE in MavenPomResolver (gradle `6.8.0-rc1`)
Issue -
State: closed - Opened by seregamorph about 4 years ago
- 5 comments
Labels: status: invalid, for: external-project
#284 - Update documentation to use implementation rather than compile configuration for example dependency declarations
Issue -
State: closed - Opened by wind57 over 4 years ago
- 2 comments
Labels: type: documentation
#283 - dependency resolution not working for subprojects
Issue -
State: closed - Opened by bradmac-ats over 4 years ago
- 1 comment
Labels: status: invalid
#282 - Spring-vault-core version is getting downgraded
Issue -
State: closed - Opened by sibidominic over 4 years ago
- 1 comment
Labels: status: invalid
#281 - Wilcard exclusions declared in an imported bom are not applied
Issue -
State: closed - Opened by wilkinsona over 4 years ago
Labels: type: bug
#280 - wrong version of guava selected when importing spring cloud dependencies bom
Issue -
State: closed - Opened by jnizet over 4 years ago
- 4 comments
Labels: status: duplicate, for: external-project
#279 - Random NPE during gradle builds
Issue -
State: closed - Opened by miensol over 4 years ago
- 5 comments
Labels: status: waiting-for-feedback, status: waiting-for-triage, status: feedback-reminder
#278 - Overriding version forces it to appear in dependencyManagement of generated POM
Issue -
State: closed - Opened by mrusinak over 4 years ago
- 7 comments
Labels: status: declined
#277 - Cannot Resolve dependent bom that matches project group/name
Issue -
State: closed - Opened by rwinch over 4 years ago
- 3 comments
Labels: status: declined
#276 - Adding the ability to exclude configurations
Issue -
State: closed - Opened by nossralf almost 5 years ago
- 1 comment
Labels: status: declined
#275 - Cache POM exclusions in Gradle daemon
Pull Request -
State: closed - Opened by banderous almost 5 years ago
- 8 comments
Labels: status: declined
#274 - Fix typo in Maven Exclusions section of the docs
Pull Request -
State: closed - Opened by minionOfZuul almost 5 years ago
- 3 comments
Labels: type: documentation
#273 - Gradle 6.3: Publication only contains dependencies and/or constraints without a version
Issue -
State: closed - Opened by flozano almost 5 years ago
- 3 comments
Labels: status: invalid
#270 - Raise the minimum supported version of Java to 8
Issue -
State: closed - Opened by wilkinsona almost 5 years ago
Labels: type: enhancement
#269 - Raise the minimum supported version of Gradle to 6.8
Issue -
State: closed - Opened by wilkinsona almost 5 years ago
- 1 comment
Labels: type: enhancement
#268 - Unexpected dynamic dependency version resolution
Issue -
State: open - Opened by GFriedrich about 5 years ago
- 10 comments
Labels: type: bug
#264 - Allow direct dependencies to have no effect on transitive dependencies if they are not overriding dependency management
Issue -
State: closed - Opened by dorongold about 5 years ago
- 2 comments
Labels: type: enhancement, status: superseded
#262 - Gradle metadata missing version information
Issue -
State: closed - Opened by brockj about 5 years ago
- 20 comments
Labels: status: superseded
#258 - Verify behaviour of dependency locking when applying dependency management
Issue -
State: open - Opened by slavashvets over 5 years ago
- 13 comments
Labels: type: task
#257 - Invalid pom is produced when using both the dependency management plugin and Gradle's bom support
Issue -
State: closed - Opened by acidbee over 5 years ago
- 12 comments
Labels: type: bug
#229 - #224 support standard Gradle dependency notation in "importPom"
Pull Request -
State: open - Opened by bsideup over 6 years ago
- 2 comments
Labels: type: enhancement
#228 - Port all tests to Java
Issue -
State: closed - Opened by wilkinsona over 6 years ago
Labels: type: task
#227 - Adopt Spring Java Format
Issue -
State: closed - Opened by wilkinsona over 6 years ago
- 1 comment
Labels: type: task, status: superseded
#225 - Effective model building for Maven poms is inefficient as models are not cached
Issue -
State: closed - Opened by moley over 6 years ago
- 16 comments
Labels: type: bug
#217 - Allow dependency without version for exclusion purposes
Issue -
State: closed - Opened by pelepelin over 6 years ago
- 7 comments
Labels: status: declined
#211 - Relationship between this plugin and Gradle's improved pom support
Issue -
State: open - Opened by twwwt almost 7 years ago
- 18 comments
Labels: type: documentation
#208 - overriding version property with a bom
Issue -
State: closed - Opened by ezraroi almost 7 years ago
- 13 comments
Labels: status: invalid
#205 - Migration to Gradle 4.6's IMPROVED_POM_SUPPORT feature?
Issue -
State: closed - Opened by avonengel almost 7 years ago
- 4 comments
Labels: status: invalid
#193 - Document how to declare a dependency using a provider to avoid problems with importedProperties and managedVersions causing premature bom resolution that interferes with subsequent dependency management and dependency configuration
Issue -
State: open - Opened by andersonkyle about 7 years ago
- 4 comments
Labels: type: documentation
#173 - Allow mavenBom to override dependency
Issue -
State: closed - Opened by rwinch almost 8 years ago
- 16 comments
Labels: type: enhancement, status: superseded
#167 - Avoid applying dependency management to dependencies with a forced version
Issue -
State: closed - Opened by JLLeitschuh almost 8 years ago
- 17 comments
Labels: type: enhancement, status: superseded
#164 - Referencing a BOM project in a multi-project build
Issue -
State: open - Opened by mjustin almost 8 years ago
- 11 comments
Labels: type: enhancement
#160 - Add option for changing version resolution strategy for multiple boms
Issue -
State: closed - Opened by xvik almost 8 years ago
- 1 comment
Labels: type: enhancement, status: superseded
#67 - Support the use of classifiers in dependency management
Issue -
State: closed - Opened by Fredericson about 9 years ago
- 9 comments
Labels: status: declined
#56 - Cannot use dependencyManagement.importedProperties when defining additional dependency management
Issue -
State: closed - Opened by wujek-srujek over 9 years ago
- 12 comments
Labels: type: bug, status: duplicate