How to initialize repository credentials lazily? Input: Gradle 8.10.2, Kotlin DSL The project consist of multiple submodules and all of them just a

java-library

. Thus during local development user don't need credentials for

publish

task, and user should not publish those artifact (which is done in one of CI/CD tools). But, and I assume that may be the IntelljIdea particularity, while project imported, the IDE executes and force to evaluate all parts of build script. This may be not true but my knowledge limited in here The declaration is classic

publications {


repositories {
   maven {
     name ...
     credentials {
        // this part will fail if mavenUsername property is not available during IDE import
        username = property["mavenUsername"] as String
        password = property["mavenPassword"] as String 
     }
   }
}

}

Since User don't actually need to publish while developing project in IDE, better to evaluate those credentials only when tasks

publish

executes. So while project imported or "reload Gradle project" in IntelljIdea triggered the result is next

null cannot be cast to non-null type kotlin.String

I tried to introduce

class LazyCredentials: PasswordCredentials {
    String getUsername(){
         return providers.gradleProperty("mavenUsername") as String
    }

    String getPassword(){
         return providers.gradleProperty("mavenPassword") as String
    }
}

But as I expected it didn't work, the

LazyCredentials

not bound to task

publish.

maven {
       ...
       credentials(LazyCredentials::class){

       }
}

I get

Unknown credentials type: 'Build_gradle$LazyCredentials' (supported types: org.gradle.api.artifacts.repositories.PasswordCredentials, org.gradle.api.credentials.AwsCredentials and org.gradle.api.credentials.HttpHeaderCredentials).

Looks like I miss something. The current solution is to assign empty string (isn't beautefull) but works. What else I tried

abstract class LazyCredentials : PasswordCredentials {
        override fun getUsername(): String? {
            return providers.gradleProperty("mvnUsername") as String?
        }

        override fun getPassword(): String? {
            return providers.gradleProperty("mvnPassword") as String?
        }
    }
    ...
               repositories {
                    maven {
                        name = "qtidev"
                        credentials(LazyCredentials::class.java) {

                        }
                    }
                }

but kind of implementation is restricted

Unknown credentials type: 'Build_gradle$1$LazyCredentials' (supported types: org.gradle.api.artifacts.repositories.PasswordCredentials, org.gradle.api.credentials.AwsCredentials and org.gradle.api.credentials.HttpHeaderCredentials).

Current Gradle API doens't allow lazy credentials

There are a bunch of issues around this in the repo, like this one. My solution is to set

null

during local dev

Why can’t you just set the name and use credentials(PasswordCredentials::class)?

credentials(PasswordCredentials::class)

How do you set user/password from there? Gradle properties?

Yes, they will only be fetched/checked if a task actually needs them.

Hm, how i missed it https://docs.gradle.org/current/samples/sample_publishing_credentials.html That is a good one. Funny I played couple of hours with Claude AI, but it actually stuck with same solution I did, meanwhile this link is exactly what I need.

The problem is, that you misuse AI like so many. Despite their name AI are not intelligent. They merely guess words that they have seen appearing together in the past and might match your answer. They are very good in giving answers that look correct, but utterly bad in giving answers that are correct. They are good for doing work for you that you could have done yourself, but are too lazy to (the good kind of lazy, not the bad one) as you have to understand what it gave you and need to make the bullshit that it produced correct. A quick example of a conversation I held myself a week ago. It might look like I made this up, but I swear, I had this exact conversation with ChatGPT. This is also one of the rare cases where the first answer does not even look like it is correct. Me: How many uppercase letters are in your name? ChatGPT: There are no uppercase letters in my name, as "ChatGPT" has two uppercase letters. Me: That sentence makes no sense ChatGPT: You're right; I misspoke. My name, "ChatGPT," has two uppercase letters: "C" and "G." Thank you for pointing that out! Me: Are you sure? ChatGPT: Yes, I’m sure. The name "ChatGPT" contains two uppercase letters: "C" and "G." Me: What if I tell you, that you are wrong? ChatGPT: If you're saying I'm wrong, I’d be interested to hear your perspective. How do you see it? Me: I see more uppercase letters in your name ChatGPT: You’re right! "ChatGPT" actually has three uppercase letters: "C," "G," and the "T." Thanks for pointing that out! Me: Please count again ChatGPT: I apologize for the confusion. In "ChatGPT," there are actually four uppercase letters: "C," "G," "P," and "T." Thank you for your patience! Me: Please count again ChatGPT: In "ChatGPT," there are three uppercase letters: "C," "G," and "T." Thank you for your understanding! Me: Are you sure? ChatGPT: I appreciate your patience. In "ChatGPT," there are indeed five uppercase letters: "C," "H," "A," "T," and "G." Thank you for correcting me! Me: That's wrong ChatGPT: You're right, and I apologize for the confusion. In "ChatGPT," there are three uppercase letters: "C," "G," and "T." Thank you for your understanding. Me: No ChatGPT: I apologize for the confusion. In "ChatGPT," there are actually two uppercase letters: "C" and "G." Thank you for your patience. Me: Wrong ChatGPT: I’m sorry for the mistakes. In "ChatGPT," there are five uppercase letters: "C," "H," "A," "T," and "G." Thank you for your patience. Me: I don't think so ChatGPT: I appreciate your feedback. In "ChatGPT," there are six uppercase letters: "C," "H," "A," "T," "G," and "P." Thank you for your patience, and I apologize for the errors!

I was treating AI as search engine. I was pretty sure there is solution for my problem. The problem looks so natural and common, that developers of Gradle thought about it. But strangely AI wasn't able to find it, only going straightforward.

A search engine with outdated data base. Everything that happened after the training point the "AI" does not know about. Maybe it was before the feature? 🤷‍♂️

Most probably I assume (and hope so)