Ignite TC Bot created IGNITE-28749:
--------------------------------------
Summary: [doc] Document thin client module extraction and artifact
usage
Key: IGNITE-28749
URL: https://issues.apache.org/jira/browse/IGNITE-28749
Project: Ignite
Issue Type: Improvement
Components: documentation
Reporter: Ignite TC Bot
Documentation follow-up for IGNITE-28717: Extraction of thin client API to
module.
Context:
- Original issue: https://issues.apache.org/jira/browse/IGNITE-28717
- Related preparatory issue: https://issues.apache.org/jira/browse/IGNITE-28733
- PR: https://github.com/apache/ignite/pull/13176
Why docs are needed:
The implementation moves thin client API classes into a dedicated module,
updates thin-client-related classpath scripts, and prepares the packaging
direction where users should not rely on ignite-core.jar for thin client usage.
The reviewed PR/commit set does not include the corresponding website/user
documentation updates for dependency selection and migration guidance.
Documentation scope:
- Explain that thin client API classes are now provided from a dedicated
thin-client module instead of being consumed through ignite-core.
- Describe which artifact(s) users should add to the classpath for thin client
applications.
- Clarify migration guidance for existing applications that used ignite-core
only to access thin client APIs.
- Mention any compatibility/runtime implications that become simpler after the
extraction, including reduced dependency on server-side implementation classes.
- Add a release-note-level mention for the affected release line if appropriate.
Likely documentation locations:
- Thin client getting started / dependency setup
- Thin client Java API introduction
- Release notes / What's New for the release line
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
