As soon as one defines a custom repository, an imp...

# scripting

[Piotr Krzemiński]

As soon as one defines a custom repository, an implicit dependency on Maven Central is gone and needs to be added explicitly.
I'm thinking about adding constants to Kotlin scripting definition that would contain URLs to Maven Central and Maven local while touching this topic, to have:

// now
@file:Repository("<https://repo1.maven.org/maven2/>")

// proposed
@file:Repository(MAVEN_CENTRAL) or @file:Repository(mavenCentral()) for parity with Gradle

and

// now
@file:Repository("file://~/.m2/repository/")

// proposed
@file:Repository(MAVEN_LOCAL) or @file:Repository(mavenLocal()) for parity with Gradle

thoughts?

[Piotr Krzemiński]

any thoughts on the preferred API?
• 1️⃣ MAVEN_CENTRAL is a convention used for constants
• 2️⃣ mavenCentral() is used in Gradle

[Adam S]

isn't option 2 impossible? Annotation args have to be compile-time constants

[Piotr Krzemiński]

ah, true! yeah, so we're left with 1️⃣ , I wouldn't like to propose any hacks to allow the second syntax

[Javier]

I would even add constants for all known repositories:

• Google
• androidx
• Gradle portal
• Snapshots
• JetBrains dev

[Javier]

Pretty annoying when I have to find some of then from one repository just to copy paste

[Piotr Krzemiński]

Gradle plugin portal repo is probably not needed in the context of Kotlin scripting, but for the rest, I totally agree

[Nikky]

also the path to mavenLocal file://~/.m2/repository ?

[Piotr Krzemiński]

proposed in the original message

[Adam S]

Maven Local can be set with a system property - https://stackoverflow.com/a/57223696/4161471. So perhaps a specific @file:MavenLocal annotation is needed that will use maven.repo.local or default to ~/.m2/repository

[Piotr Krzemiński]

created a YouTrack ticket to track it: https://youtrack.jetbrains.com/issue/KT-67861