Skip to content

docs: update offline license key docs for License Checker 2.3.1 backport (v24)#5819

Open
mcollovati wants to merge 3 commits into
v24from
docs/license-checker-2.3.1-offline-key-v24
Open

docs: update offline license key docs for License Checker 2.3.1 backport (v24)#5819
mcollovati wants to merge 3 commits into
v24from
docs/license-checker-2.3.1-offline-key-v24

Conversation

@mcollovati

@mcollovati mcollovati commented Jul 17, 2026

Copy link
Copy Markdown
Contributor

Updates the license documentation for the License Checker 2.3.1 backport, which brings mid2/offlineKeyV2 support to Vaadin 24.9.

Changes

  • articles/flow/configuration/licenses/index.adoc: change the mid2 since badge V24.10V24.9; update the machine-ID table (mid2/offlineKeyV2 for 24.9 and later, mid/offlineKey for 24.8 and earlier); correct the IMPORTANT box. The OSHI note stays V24.10 (OSHI is still bundled in License Checker 2.3.1), and the download-offline-license goal stays 24.10+.
  • articles/flow/kb/index.adoc (license troubleshooting):
    • Expand the "Detected an offline license version 1, but version 2 is required" entry to explain it can mean the V1 machine ID could not be computed — commonly a blocked/failed JNA native library — with a mvn -X / ./gradlew --debug diagnosis tip.
    • Fix the stale "24.10 and later / 24.9 and earlier" claim in the "Invalid Offline Key" entry to match the backport.

Docs issue: #5817
Related License Checker issue: vaadin/license-checker-vaadin10#245

@github-actions

github-actions Bot commented Jul 17, 2026

Copy link
Copy Markdown

AI Language Review

In the reviewed file, the following issues need improvement:

  1. Explanation of New Key Formats: In the section titled "Detected an Offline License Version 1, but Version 2 is required," the revised explanation includes a better context about the mid2 and mid keys and their reliance on certain libraries. This improvement should be maintained for clarity.

  2. Mismatched Key and Vaadin Version: In the section titled "Invalid Offline Key," the description of supported key formats relative to Vaadin versions is more detailed in the updated version. Ensure this expanded explanation remains, as it improves user understanding.

The rest of the content you provided appears necessary and relevant, enhancing the clarity and completeness of the documentation.

@mcollovati
mcollovati force-pushed the docs/license-checker-2.3.1-offline-key-v24 branch from accb4c7 to f7b14f0 Compare July 17, 2026 05:07
mid2/offlineKeyV2 support was backported to Vaadin 24.9, so it is no
longer exclusive to 24.10+. Update the mid2 since badge to V24.9, the
machine ID compatibility table, and the offline key retrieval guidance.
The download-offline-license Maven goal remains 24.10+ only, and the
OSHI note stays V24.10 (OSHI is still bundled in License Checker 2.3.1).
Explain that the 'Detected an offline license version 1, but version 2
is required' message can also mean the version 1 machine ID could not be
computed -- commonly because the JNA native library is blocked or fails
to load -- and point users to mvn -X to find the real error. Also update
the Invalid Offline Key entry so the version mismatch guidance matches
the License Checker 2.3.1 backport (mid2/offlineKeyV2 in 14.14, 23.6,
24.9 and later; download-offline-license goal still 24.10+).
- Add 'backported' to the docs vocabulary (Vale.Spelling).
- Add JNA and OSHI to the Vaadin.Abbr exceptions.
- Wrap version-specific offline-key guidance in Vaadin.Versions = NO/YES,
  matching the pattern already used elsewhere in the docs.
@mcollovati
mcollovati force-pushed the docs/license-checker-2.3.1-offline-key-v24 branch from f7b14f0 to c27a314 Compare July 17, 2026 05:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant