Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Configuring plugins versions

See original GitHub issue

To apply a plugin, we can use the plugins DSL https://docs.gradle.org/current/userguide/plugins.html#sec:plugins_block

plugins {
  id 'com.github.jk1.dependency-license-report' version '1.9'
}

The problem is replacing the hard-coded version 1.9 with Versions.gradle_license_report does not work for Groovy files.

Is there a workaround to be able to use buildSrcVersions for managing plugin dependencies as well as Library dependencies?

This is already done for the special case of buildSrcVersions itself (https://github.com/jmfayard/buildSrcVersions/issues/47) , although that only works in .kts files.

plugins {
-  id("de.fayard.buildSrcVersions") version "0.4.2"
+ buildSrcVersions
}

Issue Analytics

State:
Created 4 years ago
Comments:19 (11 by maintainers)

Top GitHub Comments

3reactions

jmfayardcommented, Sep 4, 2019

Good to know! I edited your ticket so that it can serve as documentation for people facing the same issue.

It would be nice if we were also able to use a const for the library name: id Paths.dependency-license-report version Versions.gradle_license_report

Maybe we can generate code that helps with this if we detect that Versions.currentGradleVersion >= 5.6. I will have to think about it.

1reaction

jmfayardcommented, Sep 15, 2019

@nkiesel @tadfisher @tadfisher @sigurdurrafn Check out the brand new $ ./gradlew :refreshVersions introduced in version 0.6.0 It generates gradle.properties with versions and available updates and from there you can set the plugins versions!

https://github.com/jmfayard/buildSrcVersions/issues/77

Top Results From Across the Web

Guide to Configuring Plug-ins - Apache Maven

All plugins should have minimal required information: groupId , artifactId and version . Important Note: Always define the version of each ...

Using Gradle Plugins

The plugin version is loaded from gradle.properties and configured in the settings script, allowing the plugin to be added to any project without...

Managing Plugins - Jenkins

The simplest and most common way of installing plugins is through the Manage Jenkins > Manage Plugins view, available to administrators of a...

Versions Maven Plugin – Plugin Documentation - MojoHaus

Goal Report? Description versions:revert No Restores the pom from the initial backup. versions:set‑scm‑tag No Updates the current project's SCM tag. versions:use‑next‑versions No Replaces any version with...

7.1. Configuring Maven Plugins - Sonatype Help

Maven plugins are configured using properties that are defined by goals within a plugin. If you look at a goal like the compile...