This message was deleted.

Something like this?

listOf(
  "dependency:notation:1.0",
  "anotherDependency:notation:1.0",
).forEach {
  configurations.getByName("configuration").dependencies.add(dependencies.create(provider { it }))
}

The point is that my

dependenciesProvider

is actually:

val dependenciesProvider = providers.gradleProperty("dependencies").map { it.split(',') }

and in

gradle.properties

:

dependencies=dependency:notation:1.0,anotherDependency:notation:1.0

This is still a way simpler case than mine, but the point is that my provider holds a list of dependencies, and I want to keep that resolved lazily. Currently, I ended up with:

dependenciesProvider.get().forEach {
  dependencies.add("configuration", it)
}

but that breaks the whole idea of providers.

you can use

dependencies.addAllLater()

, but you have to map the dependencies, e.g.

dependencies.addAllLater(
  dependenciesProvider.map { deps ->
    deps.map { dep -> 
      project.dependencies.create("dep")
    }
  }
)

I'm curious why the

Later

suffix vs just

addAll(Provider<Iterable<>>)

but +1 on this

Dang, I’ve been using that already few months ago. 🤦‍♂️ Thanks, Adam!

my pleasure!

Oh, but there’s no

addAllLater

in

DependencyHandler

.

uh oh...

It's on

Configuration.dependencies

I can’t go another way — it’s all done having

DependencyHandler

as a starting point. 🤷

Looks like you have the

configurations

up there

addAllLater

does not have

action

as it takes a

Provider<Iterable<Dependency>>

. The configuration

action

would be where you create

Dependency

. Another option is to use

configurations.getByName(configurationName).withDependencies { ... }

. It is more meant to for example last-minute add some dependencies based on already declared dependencies, but you could also do it there. It is executed last-minute right before the dependencies are going to be resolved.

Awesome, this did the job — a sudden issue was resolved in a pretty nice way. https://github.com/JetBrains/gradle-intellij-plugin/blob/071da761e66f6b9db4270523d[…]form/gradle/extensions/IntelliJPlatformDependenciesExtension.kt Thank you, everyone! 🙇 🙌

Why did you mix both approaches?

You mean

configurations.getByName(configurationName).withDependencies {}

and

dependencies.addProvider(configurationName, ...)

in one class?

No,

.withDependencies { add }

and

dependencies.addAllLater

.

Apparently, I need to use

dependencies.addAllLater

as

.withDependencies { add }

simply doesn’t resolve providers.

The two approaches I mean are

configurations.getByName(configurationName).withDependencies {
    addAll(ids.get().map { createIntelliJPlatformBundledPluginDependency(it).apply(action) })
}

or

configurations.getByName(configurationName).withDependencies {
    ids.get().forEach { add(createIntelliJPlatformBundledPluginDependency(it).apply(action)) }
}

and

configurations.getByName(configurationName).dependencies.addAllLater(ids.map {
    it.map { id ->
        createIntelliJPlatformBundledPluginDependency(id).apply(action)
    }
})

In

withDependencies

there is not really a need to continue using providers. This action is executed right before dependency resolution. So using

addLater

or

addAllLater

within

withDependencies

is imho unneccessary and just makes things a tad bit slower and the code more complex.