tree 4b2eb3d1124ee4c40e17cc4700a987dc23f9eadf
parent 7d0015359dfac8532e408b6be67cee262c605c87
author Farid Zakaria <farid.m.zakaria@gmail.com> 1756335875 -0700
committer GitHub <noreply@github.com> 1756335875 +0100
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsFcBAABCAAQBQJor48DCRC1aQ7uu5UhlAAAFygQAFcaewXNR2Oz50TEnBV/sSCQ
 75BtoQf7ac2XKtyh1P6q0VBuocOA5cuZmw7SUA/FaJiAI57Q3LlVjMIlxOfvl487
 fzH7pYAigbCib/rNgpA2gquATOPcjquFzHoDbL0oySqCdQ23aM223L68up9p8qvF
 9Ht7OFOypUp/YiSxG8SlAJCWBI9107bAK7XMqM9ySgHhcQi/LZUG0ifYJO/RjLvA
 8jg3nyCrMN3ATcChikGcAqjo2MQfUoGWK3D9fl4bdVLYaw96Gl2NKYXdFGzVSkE+
 NUVCGusBHoYpKvVUqxDS7VgTRwAzv8N6BpRrFrfSZrDtPKH3qM50Z+iKf8+5mN2h
 YhH0A9It4A2pgEpaZQh7rdih3b+JCCDPCPW4NmAofz+1aXHeur7Vym+6frURvjNP
 G/nzr5VoNA4G1GDbg92L9jC51+p9LmBr2Hc+//yQsILEz2ltSrfQVrLktjanEsg+
 cHMi3gCSLfULkLrk3F1Xq1iwAjsqnEn6SKY2WJ3M4+CzTH5i5pLz00+gmp+sd8zi
 d/FXLnRckgBbsVnHAFkO+AaUNg8WhEPL5rcjKgDsZ6rZo73iTXNWBvaorPUMEwtr
 Sv2bNOrNzUzp0GsiuxSAdr2JzzvtRPG5QorIn4Lpl9lweSkBPmbuN20xOTRHkUgJ
 gj8m78ZLT41+gsQytCyH
 =dhp3
 -----END PGP SIGNATURE-----
 

Add support for publishing maven-metadata.xml (#1260)

Maven repositories normally have a maven-metadata.xml file that indicate to the Maven system what versions are available and which is to be considered the latest version.

```xml
<metadata modelVersion="1.1.0">
    <groupId>com.mycompany.app</groupId>
    <artifactId>my-app</artifactId>
    <versioning>
        <latest>1.0</latest>
        <release>1.0</release>
        <versions>
            <version>1.0</version>
        </versions>
        <lastUpdated>20200731090423</lastUpdated>
    </versioning>
</metadata>
```

At Confluent, we use AWS Code Artifactory which does not mark a Maven package as "published" unless a new maven-metadata.xml is uploaded indicating so.

Add support for reading existing maven-metadata.xml
Add support for adding the new version to the metadata object
Add support to upload the file for http, file, s3 protocols

Co-authored-by: Vince Rose <vrose@confluent.io>
Co-authored-by: Na Lou <nlou@confluent.io>