Looly
|
479c4837c8
|
prepare 5.4.4
|
2020-09-18 16:55:15 +08:00 |
|
Looly
|
870ea9a329
|
release 5.4.3
|
2020-09-18 15:57:15 +08:00 |
|
Looly
|
355c5c163b
|
fix code
|
2020-09-16 16:16:37 +08:00 |
|
Looly
|
31c211c096
|
fix test
|
2020-09-15 22:27:57 +08:00 |
|
Looly
|
ddd173a17c
|
add test
|
2020-09-14 21:11:32 +08:00 |
|
Looly
|
999c1d80d4
|
fix code
|
2020-09-14 19:06:06 +08:00 |
|
Looly
|
f05883a53a
|
add ECKeyUtil
|
2020-09-13 09:34:35 +08:00 |
|
Looly
|
58b1cae320
|
add ECKeyUtil
|
2020-09-13 03:43:33 +08:00 |
|
Looly
|
0863461a18
|
prepare 5.4.3
|
2020-09-09 17:23:46 +08:00 |
|
Looly
|
2212ee7705
|
release 5.4.2
|
2020-09-08 20:59:52 +08:00 |
|
Looly
|
025728e389
|
add comment and test
|
2020-09-01 15:53:16 +08:00 |
|
zhuqianchao
|
0e9909ffeb
|
1. 在使用阻塞等待获取锁的方式中,必须在try代码块之外,并且在加锁方法与try代码块之间没有任何可能抛出异常的方法调用,避免加锁成功后,在finally中无法解锁。
说明一:如果在lock方法与try代码块之间的方法调用抛出异常,那么无法解锁,造成其它线程无法成功获取锁。
说明二:如果lock方法在try代码块之内,可能由于其它方法抛出异常,导致在finally代码块中,unlock对未加锁的对象解锁,它会调用AQS的tryRelease方法(取决于具体实现类),抛出IllegalMonitorStateException异常。
说明三:在Lock对象的lock方法实现中可能抛出unchecked异常,产生的后果与说明二相同。 java.concurrent.LockShouldWithTryFinallyRule.rule.desc
2. 补上遗漏的Override注解
|
2020-08-29 17:22:36 +08:00 |
|
Looly
|
50c30259cb
|
prepare 5.4.2
|
2020-08-29 15:25:30 +08:00 |
|
Looly
|
3ffffe3d3b
|
release 5.4.1
|
2020-08-29 15:07:08 +08:00 |
|
Looly
|
68ad664fec
|
fix test
|
2020-08-29 11:43:10 +08:00 |
|
Looly
|
5be24863d1
|
prepare 5.4.1
|
2020-08-16 13:06:13 +08:00 |
|
Looly
|
2edf6f65cc
|
release 5.4.0
|
2020-08-16 12:10:34 +08:00 |
|
Looly
|
04917da6e2
|
nio enhancement
|
2020-08-01 18:58:44 +08:00 |
|
Looly
|
026afb641f
|
add method
|
2020-07-25 18:06:08 +08:00 |
|
Looly
|
baa8ddd9ed
|
prepare 5.3.11
|
2020-07-23 18:21:00 +08:00 |
|
Looly
|
1f19a31c5a
|
release 5.3.10
|
2020-07-23 18:07:43 +08:00 |
|
Looly
|
b47125c9f1
|
fix bug and add crypto
|
2020-07-23 12:10:58 +08:00 |
|
Looly
|
fb2596b6c7
|
prepare 5.3.10
|
2020-07-12 13:00:02 +08:00 |
|
Looly
|
8236ae61f2
|
release 5.3.9
|
2020-07-12 12:28:17 +08:00 |
|
Looly
|
01f19daa66
|
prepare 5.3.9
|
2020-06-17 15:34:36 +08:00 |
|
Looly
|
ceb8f868f2
|
release 5.3.8
|
2020-06-17 02:16:27 +08:00 |
|
Liang Long
|
422ce00478
|
modify BaseAsymmetric.java
修改了getPrivateKeyBase64()方法,防止因未传入私钥而带来的空指针异常。
|
2020-06-16 12:15:36 +08:00 |
|
Looly
|
8319b00918
|
add test
|
2020-06-05 10:10:02 +08:00 |
|
Looly
|
9ca7d93f70
|
prepare 5.3.8
|
2020-06-03 18:51:56 +08:00 |
|
Looly
|
78f57d7ffd
|
release 5.3.7
|
2020-06-03 18:48:35 +08:00 |
|
Looly
|
670cb3c10b
|
fix buf
|
2020-06-02 17:30:37 +08:00 |
|
Looly
|
0b74d3769d
|
prepare 5.3.7
|
2020-05-31 18:00:07 +08:00 |
|
Looly
|
62e02e877a
|
release 5.3.6
|
2020-05-31 17:30:02 +08:00 |
|
Looly
|
44fe8904a2
|
remove EC
|
2020-05-26 18:21:42 +08:00 |
|
zz
|
34d646bd88
|
fix annotation in StrUtil and SymmetricCrypto
|
2020-05-17 18:50:15 +08:00 |
|
Looly
|
5e381a1007
|
prepare 5.3.6
|
2020-05-14 02:19:43 +08:00 |
|
Looly
|
3da83e0227
|
release 5.3.5
|
2020-05-13 21:22:54 +08:00 |
|
Looly
|
58fab104c7
|
prepare 5.3.5
|
2020-05-10 08:50:33 +08:00 |
|
Looly
|
c2d70a4613
|
release 5.3.4
|
2020-05-10 00:14:29 +08:00 |
|
Looly
|
fdf735fa05
|
prepare 5.3.4
|
2020-05-06 08:24:09 +08:00 |
|
Looly
|
bf65fa3c5f
|
fix bug
|
2020-05-05 23:49:41 +08:00 |
|
Looly
|
513fb1c861
|
release 5.3.3
|
2020-05-05 23:24:00 +08:00 |
|
Looly
|
c697de539f
|
add TOPT
|
2020-04-30 12:01:35 +08:00 |
|
Looly
|
ea96eecd4b
|
add opt
|
2020-04-30 09:11:22 +08:00 |
|
Looly
|
669d19eab8
|
prepare 5.3.3
|
2020-04-23 15:20:05 +08:00 |
|
Looly
|
d6125c1bf7
|
release 5.3.2
|
2020-04-23 14:31:42 +08:00 |
|
Looly
|
d3e547515a
|
prepare 5.3.2
|
2020-04-17 18:33:24 +08:00 |
|
Looly
|
edd47d6c86
|
release 5.3.1
|
2020-04-17 18:15:22 +08:00 |
|
Looly
|
2f9fa2c29a
|
sm2 support encoding
|
2020-04-17 17:09:16 +08:00 |
|
Looly
|
ca7c407a1c
|
add UrlDecoder
|
2020-04-16 01:13:58 +08:00 |
|