Skip to content

Commit d2407c2

Browse files
committedJul 2, 2023
chore(ci): add JDK 20/21-ea into GitHub CI 🤖
1 parent 2b82722 commit d2407c2

File tree

3 files changed

+3
-3
lines changed

3 files changed

+3
-3
lines changed
 

‎.github/workflows/ci.yaml

+1-1
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ jobs:
1010
strategy:
1111
matrix:
1212
os: [ ubuntu-latest, windows-latest ]
13-
java: [ 8, 11, 17, 19, 20-ea ]
13+
java: [ 8, 11, 17, 19, 20, 21-ea ]
1414
fail-fast: false
1515
max-parallel: 64
1616
name: Test JDK ${{ matrix.java }}, ${{ matrix.os }}

‎README-EN.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -57,7 +57,7 @@
5757
# 🔧 Functions
5858

5959
👉 `TransmittableThreadLocal`(`TTL`): The missing Java™ std lib(simple & 0-dependency) for framework/middleware,
60-
provide an enhanced `InheritableThreadLocal` that transmits values between threads even using thread pooling components. Support `Java 6~19`.
60+
provide an enhanced `InheritableThreadLocal` that transmits values between threads even using thread pooling components. Support `Java 6~21`.
6161

6262
Class [`InheritableThreadLocal`](https://docs.oracle.com/javase/10/docs/api/java/lang/InheritableThreadLocal.html) in `JDK`
6363
can transmit value to child thread from parent thread.

‎README.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -60,7 +60,7 @@
6060

6161
# 🔧 功能
6262

63-
👉 `TransmittableThreadLocal`(`TTL`):在使用线程池等会池化复用线程的执行组件情况下,提供`ThreadLocal`值的传递功能,解决异步执行时上下文传递的问题。一个`Java`标准库本应为框架/中间件设施开发提供的标配能力,本库功能聚焦 & 0依赖,支持`Java 6~20`
63+
👉 `TransmittableThreadLocal`(`TTL`):在使用线程池等会池化复用线程的执行组件情况下,提供`ThreadLocal`值的传递功能,解决异步执行时上下文传递的问题。一个`Java`标准库本应为框架/中间件设施开发提供的标配能力,本库功能聚焦 & 0依赖,支持`Java 6~21`
6464

6565
`JDK`[`InheritableThreadLocal`](https://docs.oracle.com/javase/10/docs/api/java/lang/InheritableThreadLocal.html)类可以完成父线程到子线程的值传递。但对于使用线程池等会池化复用线程的执行组件的情况,线程由线程池创建好,并且线程是池化起来反复使用的;这时父子线程关系的`ThreadLocal`值传递已经没有意义,应用需要的实际上是把 **任务提交给线程池时**`ThreadLocal`值传递到 **任务执行时**
6666

0 commit comments

Comments
 (0)
Please sign in to comment.