This message was deleted Gradle Community #community-support

This message was deleted.

Slackbot

05/16/2022, 12:41 PM

This message was deleted.

Martin

05/16/2022, 12:44 PM

It should work if you use a plugin from your included build you should have its dependencies available on your main project buildscript classpath

Martin

05/16/2022, 12:45 PM

either declare a "placeholder" plugin in your included build that you apply in your main build

Martin

05/16/2022, 12:45 PM

or do something "old style" like:

Copy code

buildscript {
  dependencies {
    // pull the included build here
    classpath("com.example:build-logic")
  }
}

Marco Romano

05/16/2022, 12:46 PM

I’ve found out there are cases I needed plugin X in the main build but not in the build logic, but I was still depending on plugin X from within

buildSrc

because I found out it was a simple way to make it available to the main build as well.

Martin

05/16/2022, 12:47 PM

Yea, I like to do that as well, ensures all the dependencies are resolved at the same time

Marco Romano

05/16/2022, 12:47 PM

does this mean I can’t really ditch buildSrc completely?

Martin

05/16/2022, 12:47 PM

I think you can?

Martin

05/16/2022, 12:48 PM

Using one of the 2 solutions above you can pull your included build dependencies into your main build

🙏 1

Marco Romano

05/16/2022, 3:04 PM

I’ve resorted to using buildscript dependencies as you suggested. I’ve also noticed from here it should be possible to declare plugin versions in the

pluginManagement.plugins

block. It works indeed but I can’t access the version catalog from within this block, is this a known limitation or am I doing something wrong?

4 Views