[
https://issues.apache.org/jira/browse/IGNITE-28887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Pavlov reassigned IGNITE-28887:
--------------------------------------
Assignee: Ignite TC Bot
> [doc] Document Spring 6 and Jakarta Transaction migration
> ---------------------------------------------------------
>
> Key: IGNITE-28887
> URL: https://issues.apache.org/jira/browse/IGNITE-28887
> Project: Ignite
> Issue Type: Task
> Components: documentation
> Reporter: Ignite TC Bot
> Assignee: Ignite TC Bot
> Priority: Major
> Labels: ise
> Time Spent: 10m
> Remaining Estimate: 0h
>
> IGNITE-28588 updates Apache Ignite to Spring 6.2.19, Jetty 12.1.x, and
> Jakarta Transaction 2.0.1. The merged PR apache/ignite#13342 changes public
> integration surfaces, including ignite-jta API imports from
> javax.transaction.TransactionManager to
> jakarta.transaction.TransactionManager, Jetty 12 module coordinates, and the
> Maven enforcer rule that bans old javax.transaction artifacts.
> Documentation should be updated with the minimal user-facing migration notes:
> * docs/_docs/setup.adoc: mention that ignite-jta uses jakarta.transaction-api
> 2.0.1+ after the Spring 6 update.
> * docs/_docs/extensions-and-integrations/spring/spring-tx.adoc and
> spring-caching.adoc: verify dependency snippets for Spring 6 compatibility
> and add a short note that applications using JTA transaction manager lookups
> must compile against jakarta.transaction.TransactionManager.
> * If needed, mention Jetty 12 / Jakarta Servlet compatibility for
> ignite-rest-http and ignite-web where module setup is documented.
> Source issue: IGNITE-28588. Related source issue: IGNITE-28765. Merged PR:
> https://github.com/apache/ignite/pull/13342.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
