Interesting, I wasn’t aware of this. I published these snapshot artifacts (dry-run) with the "mvn deploy" command after modifying my settings.xml as follows:
<settings xmlns="http://maven.apache.org/SETTINGS/1.0.0"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0 https://maven.apache.org/xsd/settings-1.0.0.xsd";> <servers> <!-- To publish a snapshot of your project --> <server> <id>apache.snapshots.https</id> <username>bchapuis</username> <password>XXXXX</password> </server> <!-- To stage a release of your project --> <server> <id>apache.releases.https</id> <username>bchapuis</username> <password>XXXXX</password> </server> </servers> </settings> My intent was to execute the "./mvnw clean deploy -Papache-release” command to deploy the artifacts. I believe the apache-release profile is defined in the parent pom of the apache projects. I looked into nexus to find the drop and release buttons, but they are not available for my snapshots. I have to delete them manually from the artifact panel on the bottom left. Maybe they will appear with once the apache-release profile is activated. Bertil > On 27 Nov 2024, at 02:28, Julian Hyde <jhyde.apa...@gmail.com> wrote: > > When you press the “release” button in Nexus the artifacts will be deployed > to maven central. They appear with a latency of a couple of hours. > > (This time, because the vote failed, you should press “drop” rather than > “release”.) > > Julian > >> On Nov 26, 2024, at 14:43, Bertil Chapuis <bchap...@gmail.com> wrote: >> >> Hello Everyone, >> >> As part of the current (or maybe the next) release, I’d like to publish >> artifacts on Maven Central. While I’ve successfully published snapshots on >> Nexus [1], an additional vote may be required to proceed with releasing them. >> >> Is anyone experienced with or interested in this process? I’d appreciate any >> guidance or collaboration to ensure everything goes smoothly (you may have >> noticed a few of my recent missteps ;-). >> >> The main goal is to make our submodules accessible to other projects. For >> example, I believe our codecs (such as OpenStreetMap, GeoParquet, PMTiles, >> etc.) could find valuable use and integration beyond Baremaps once the >> artifacts are available. >> >> Looking forward to your thoughts! >> >> Best regards, >> >> Bertil >> >> >> [1] https://repository.apache.org/#nexus-search;quick~baremaps >> >> >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscr...@baremaps.apache.org >> For additional commands, e-mail: dev-h...@baremaps.apache.org >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@baremaps.apache.org > For additional commands, e-mail: dev-h...@baremaps.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@baremaps.apache.org For additional commands, e-mail: dev-h...@baremaps.apache.org
