
Benjamin Yolken
When a Java SDK build completes successfully, Stainless will generate a hosted Maven repo that can be shared for early testing, before the SDK is formally released.
The details on how to use this repo are visible when clicking on the info icon in the “Build” row in the build status panel in the studio. We also generate a custom doc page in the repo root, which is viewable by clicking on the “Learn more” link in the popup.
A similar feature has been available for Python and Typescript builds for a while; with this change, sharing and testing pre-release Java builds is just as easy.

Benjamin Yolken
When a Java SDK build completes successfully, Stainless will generate a hosted Maven repo that can be shared for early testing, before the SDK is formally released.
The details on how to use this repo are visible when clicking on the info icon in the “Build” row in the build status panel in the studio. We also generate a custom doc page in the repo root, which is viewable by clicking on the “Learn more” link in the popup.
A similar feature has been available for Python and Typescript builds for a while; with this change, sharing and testing pre-release Java builds is just as easy.

Benjamin Yolken
When a Java SDK build completes successfully, Stainless will generate a hosted Maven repo that can be shared for early testing, before the SDK is formally released.
The details on how to use this repo are visible when clicking on the info icon in the “Build” row in the build status panel in the studio. We also generate a custom doc page in the repo root, which is viewable by clicking on the “Learn more” link in the popup.
A similar feature has been available for Python and Typescript builds for a while; with this change, sharing and testing pre-release Java builds is just as easy.

Tomer Aberbach
Although the generated Java/Kotlin SDKs use reflection, they can be made usable in GraalVM by publishing them with reachability metadata. This can be enabled by setting targets.{java,kotlin}.publish.graalvm_metadata to true.
GraalVM should automatically detect and use the published metadata, but manual configuration is also available for end-users.

Tomer Aberbach
Although the generated Java/Kotlin SDKs use reflection, they can be made usable in GraalVM by publishing them with reachability metadata. This can be enabled by setting targets.{java,kotlin}.publish.graalvm_metadata to true.
GraalVM should automatically detect and use the published metadata, but manual configuration is also available for end-users.

Tomer Aberbach
Although the generated Java/Kotlin SDKs use reflection, they can be made usable in GraalVM by publishing them with reachability metadata. This can be enabled by setting targets.{java,kotlin}.publish.graalvm_metadata to true.
GraalVM should automatically detect and use the published metadata, but manual configuration is also available for end-users.

Tomer Aberbach
The generated Java/Kotlin SDKs can now include an automatically generated Spring Boot starter package to simplify configuration for users who use Spring Boot.
This can be enabled by setting targets.{java,kotlin}.publish.spring_boot_starter to true in the Stainless config.

Tomer Aberbach
The generated Java/Kotlin SDKs can now include an automatically generated Spring Boot starter package to simplify configuration for users who use Spring Boot.
This can be enabled by setting targets.{java,kotlin}.publish.spring_boot_starter to true in the Stainless config.

Tomer Aberbach
The generated Java/Kotlin SDKs can now include an automatically generated Spring Boot starter package to simplify configuration for users who use Spring Boot.
This can be enabled by setting targets.{java,kotlin}.publish.spring_boot_starter to true in the Stainless config.

Tomer Aberbach
The Java and Kotlin SDKs now support server variables in base URLs. If your OpenAPI spec includes templated URLs like https://{username}.example.com:{port}/{basePath}, the generated SDK will expose configuration options to fill in {username}, {port}, or {basePath}.

Tomer Aberbach
The Java and Kotlin SDKs now support server variables in base URLs. If your OpenAPI spec includes templated URLs like https://{username}.example.com:{port}/{basePath}, the generated SDK will expose configuration options to fill in {username}, {port}, or {basePath}.

Tomer Aberbach
The Java and Kotlin SDKs now support server variables in base URLs. If your OpenAPI spec includes templated URLs like https://{username}.example.com:{port}/{basePath}, the generated SDK will expose configuration options to fill in {username}, {port}, or {basePath}.