This message was deleted.

This message was deleted.

This message was deleted.

This message was deleted.

This message was deleted.

This message was deleted.

This message was deleted.

This message was deleted.

This message was deleted.

This message was deleted.

This message was deleted.

This message was deleted.

A problem occurred configuring project ':flutter_plugin_android_lifecycle'.

Could not load compiled classes for build file 'C:\src\flutter\.pub-cache\hosted\pub.dartlang.org\flutter_plugin_android_lifecycle-2.0.6\android\build.gradle' from cache.

Failed to notify project evaluation listener.

> Could not get unknown property 'android' for project ':flutter_plugin_android_lifecycle' of type org.gradle.api.Project. > Could not get unknown property 'android' for project ':flutter_plugin_android_lifecycle' of type org.gradle.api.Project.

This message was deleted.

This message was deleted.

This message was deleted.

Hello, I built a custom plugin which produces a zip artifact (schema resources) and potentially a jar artifact. Due to cosumer considerations - we need to care for Maven clients - the jar artifact is published under different coordinates than the main zip artifact. This is done by modifying the

artifactId

of the publication for the java artifact. This all works pretty well - except for the case where a project of this kind is being used in a multiproject build using a project reference. While Gradles dependency resolution can still work out the correct dependency via the artifact capabilities, publishing the dependent project fails with the infamous:

Publishing is not able to resolve a dependency on a project with multiple publications that have different coordinates.

project A: -> produces

group:a

(zip) -> produces

group:a-java

(jar) project B -> declares dependency

implementation(project(":a"))

Is there a workaround to coerce publishing of B to choose the correct coordinates (

group:a-java

)?

Hello, I would like to get some help how to configure a Gradle build that will include certain dependencies based on a project "variant". For example, when building the application intended for performance test deployment, certain "performance metrics" dependencies will need to be included in the assembled application. When building the application intended for production use, these "performance metrics" dependencies should be excluded. Is there a way in Gradle on how to get this configured? I'm currently looking at the "feature variants" capability in Gradle. Would this be applicable? https://docs.gradle.org/current/userguide/feature_variants.html

This message was deleted.

This message was deleted.

This message was deleted.

This message was deleted.

This message was deleted.

This message was deleted.

I’m trying to create a gradle plugin in .kts format, and am looking at a Groovy one to take some inspiration. At one point I see this code in Groovy

def dirRes = project.android.sourceSets.findByName("main").res.srcDirs.first()

. My immediate question is, how do I get the same

android

type from project if I don’t know what to ask for, in Groovy is seems to “just work” but in Kotlin I guess I need to do something like find it by name and specify what type it is so that I can then do

.sourceSets

on it etc. But the more general question may also be, is there an obvious way of how to find what I am looking for when going from Groovy -> Kotlin? As someone who’s never done something like this before and has never done Groovy before I don’t see any obvious way to do this.

This message was deleted.

This message was deleted.

This message was deleted.

This message was deleted.

This message was deleted.