Fiouz

> also, you can use in your readme file the way how to use git properties in a modern way) > > ``` > version = project.provider{project.ext.gitProps['git.commit.id.abbrev']} > ``` >...

PR modified to adopt a safer and more generic approach; instead, we use a system property to pass a JSON-encapsulated value around (we rely on Groovy JsonOutput/JsonSlurper): - no need...

This seems to work as expected: ```kotlin external interface SomeInterface inline operator fun SomeInterface.invoke(x: Any, y: Any): Boolean { return asDynamic()(x, y).unsafeCast() } ```

The issue is filled here as 1. It seems widespread among Spring Cloud subprojects, so it led me to try to identify the common element regarding publishing to Maven Central...

From past experiences with [maven-deploy-plugin](https://maven.apache.org/plugins/maven-deploy-plugin/) with private repositories (also using Sonatype Nexus), the Maven plugin itself will first download `maven-metadata.xml`, in order to upload an updated version which includes the...

At its core, the issue is: * spring-cloud-stream-dependencies 3.1.3 does exist (as seen [here](https://search.maven.org/artifact/org.springframework.cloud/spring-cloud-stream-dependencies/3.1.3/pom) or [here](https://repo1.maven.org/maven2/org/springframework/cloud/spring-cloud-stream-dependencies/3.1.3/)) * So it should be listed under [`maven-metadata.xml`](https://repo1.maven.org/maven2/org/springframework/cloud/spring-cloud-stream-dependencies/maven-metadata.xml), but it is not (I also...

Should I [request Maven Central](https://issues.sonatype.org/projects/MVNCENTRAL/summary) to repair Spring Cloud artifacts metadata? My concern is that: - I cannot claim ownership of the affected artifacts - I will not be able...