Partial release of 477 ?

[nielsbasjes]

Seems like something went wrong with the 477 release.
This one is available https://central.sonatype.com/artifact/io.trino/trino-spi in 477 (also trino-root)

The rest is still at 476 https://central.sonatype.com/search?namespace=io.trino&sort=published

[martint]

Releases are now under https://github.com/trinodb/trino/releases

[nielsbasjes]

So no longer pushed to maven central?

[martint]

The binary packages are now on github due to limitations Sonatype started imposing a few months ago. Maven central now only contains the dependencies used for development.

[nielsbasjes]

The dependencies I have used for my plugin development (specifically testing) are no longer available.
https://github.com/nielsbasjes/yauaa/blob/0ba4d77eec8111905f12a35f3e4c76e08ca70831/udfs/trino/pom.xml#L61-L81

    <dependency>
      <groupId>io.trino</groupId>
      <artifactId>trino-main</artifactId>
      <version>${trino.version}</version>
      <type>test-jar</type>
      <scope>test</scope>
    </dependency>

    <dependency>
      <groupId>io.trino</groupId>
      <artifactId>trino-testing</artifactId>
      <version>${trino.version}</version>
      <scope>test</scope>
      <exclusions>
        <exclusion>
          <groupId>org.testng</groupId>
          <artifactId>testng</artifactId>
        </exclusion>
      </exclusions>
    </dependency>

What is the new approach for these?

[nielsbasjes]

Seems the trino-main is no longer needed.

[martint]

We’re going to publish dependencies used for development - just sorting out the kinks from the migration.

However, keep in mind that many of this does are not meant for public consumption. They are internal project artifacts and there are no guarantees of backward compatibility.