Skip to content

spring-gradle-plugins/dependency-management-plugin

View on GitHub ↗Related repositories →

A Gradle plugin that provides Maven-like dependency management functionality

active 2023-08-152026-03-04 (UTC)

Complete coverage26,516 / 26,516 hourly files (100%) · 2 absent upstream2023-08-152026-08-23 (UTC)
Events
344
Pushes
30
Pull requests
17
Issues
62
Stars
73
Forks
12

Activity over time

Daily event counts in the loaded window

Line chart, 933 days from 2023-08-15 to 2026-03-04. Pushes: 30 total, peak 7 in a day. Pull requests: 17 total, peak 3 in a day. Issues: 62 total, peak 3 in a day. Comments: 133 total, peak 8 in a day. Stars: 73 total, peak 2 in a day.

  • Pushes
  • Pull requests
  • Issues
  • Comments
  • Stars

Stars, PRs, issues and forks are under-captured in the later part of this window. GH Archive progressively stopped capturing non-push events during 2026 — −95% or worse by the end of the window. Every series here except Pushes fades for that reason, so a decline above reflects the archive, not this repository. Pushes stay reliable throughout, so read them, and the contributor counts derived from them, as the real signal. Data health has the measurements.

Top contributors

Pushes, PRs, issues, reviews and comments — stars and forks excluded, so this is contribution rather than popularity

Recent activity

Latest issues, pull requests and releases

  • Issue comment#410wilkinsona2025-10-22 15:01
    Plugin changes versions of configurations not related to source sets
  • Issue comment#409tjwatson2025-09-16 20:05
    Building a WAR with Spring Boot 4.0.0-M2 causes too much to be placed in WEB-INF/lib-provided
  • Issue#409wilkinsona2025-09-16 19:54
    Building a WAR with Spring Boot 4.0.0-M2 causes too much to be placed in WEB-INF/lib-provided
  • Issue comment#408jxblum2025-06-25 21:50
    `applyMavenExclusions` set to `false` has no effect
  • Issue comment#408jxblum2025-06-24 18:38
    `applyMavenExclusions` set to `false` has no effect
  • Issue#408jxblum2025-06-24 18:31
    `applyMavenExclusions` set to `false` has no effect
  • Issue comment#407Tapchicoma2025-06-03 11:31
    Exclude well-known Kotlin Gradle plugin internal configurations
  • Issue comment#407Tapchicoma2025-06-03 09:31
    Exclude well-known Kotlin Gradle plugin internal configurations
  • Issue#407Tapchicoma2025-05-28 15:25
    Exclude well-known Kotlin Gradle plugin internal configurations
  • Issue#406wilkinsona2025-05-28 12:34
    The plugin should not create a dependency rule for direct dependencies
  • Issue comment#330jordanjennings2025-05-19 20:13
    Apply dependency management as constraints
  • Issue comment#392wilkinsona2025-04-15 12:00
    Do not apply PomDependencyManagementConfigurer when POM customization is disabled
  • Issue comment#392artemy-osipov2025-04-15 11:56
    Do not apply PomDependencyManagementConfigurer when POM customization is disabled
  • Issue comment#392wilkinsona2025-04-15 11:40
    Do not apply PomDependencyManagementConfigurer when POM customization is disabled
  • Pull request#392wilkinsona2025-04-15 11:40
  • Issue comment#403wilkinsona2025-04-15 11:36
    dependencyManagement task is eagerly created
  • Pull request#403wilkinsona2025-04-15 11:36
  • Issue#405wilkinsona2025-04-15 11:34
    Performance degradation during Gradle configuration phase since version 1.1.6
  • Issue comment#330igormukhin2025-02-11 15:09
    Apply dependency management as constraints
  • Issue comment#403alexei-osipov2025-02-03 23:39
    Use TaskContainer.register
  • Issue comment#405KarboniteKream2025-01-31 12:06
    Performance degradation during Gradle configuration phase since version 1.1.6
  • Issue#405KarboniteKream2025-01-31 10:45
    Performance degradation during Gradle configuration phase since version 1.1.6
  • Issue comment#404wilkinsona2025-01-27 14:49
    Maven Publish fails when no version specified
  • Issue#404wilkinsona2025-01-27 14:48
    Maven Publish fails when no version specified
  • Issue#404gurpreetsingh852025-01-27 04:35
    Maven Publish fails when no version specified

Totals cover only the window loaded into ClickHouse and count events, not GitHub's lifetime totals — 73 stars here means stars gained during the window, not the repo's star count.