From 7d66e63707f1a500ab6c57e034efa3fe1ff2e915 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Yann=20C=C3=A9bron?= Date: Wed, 1 Mar 2023 16:45:44 +0100 Subject: [PATCH] build_number_ranges.md: clarify Java compatibility --- topics/basics/getting_started/build_number_ranges.md | 1 + 1 file changed, 1 insertion(+) diff --git a/topics/basics/getting_started/build_number_ranges.md b/topics/basics/getting_started/build_number_ranges.md index 8bc507281..8ace573ce 100644 --- a/topics/basics/getting_started/build_number_ranges.md +++ b/topics/basics/getting_started/build_number_ranges.md @@ -64,6 +64,7 @@ Usually you should omit the product ID and use only the branch number and build > When supporting multiple major versions, it is strongly recommended to build against the _lowest_ supported version to guarantee backwards-compatibility. +In the case of supporting a range of platform versions with different underlying Java level it is _required_. See [](verifying_plugin_compatibility.md) for tooling support to ensure compatibility with chosen version range and IDEs. Consult [Incompatible API Changes](api_changes_list.md) and [Notable API Changes](api_notable.md) for an overview of known breaking and relevant changes.