Project:
| View Revisions: Issue #53488 | [ All Revisions ] [ Back to Issue ] | ||
| Summary | 0053488: Remove "net.bytebuddy.experimental" flag usage | ||
| Revision | 2023-09-20 15:59 by shuehner | ||
| Description | With the fix for 0053411 the usage of the "net.bytebuddy.experimental" flag was added to the ant tasks that execute junit tests as a temporary workaround in order to avoid failures in the mockito tests when using JDK 22. It looks like this is can be fixed by upgrading bytebuddy library version. See[1]. [1] https://github.com/raphw/byte-buddy/issues/1396 [^] From that issue looks like minimum version needed to include the fix is 1.14.3 https://github.com/raphw/byte-buddy/releases/tag/byte-buddy-1.14.3 [^] Connection is not obvious but via: - March 28 in issue said releasing fix - Issue having "Need more recent asm" - that 1.14.3 release came out same day including "Update ASM" Note: That this version is recent enough is inferred from above. But not tested. |
||
| Revision | 2023-09-19 11:02 by caristu | ||
| Description | With the fix for 0053411 the usage of the "net.bytebuddy.experimental" flag was added to the ant tasks that execute junit tests as a temporary workaround in order to avoid failures in the mockito tests when using JDK 22. It looks like this is can be fixed by upgrading to the latest bytebuddy library version. See[1]. [1] https://github.com/raphw/byte-buddy/issues/1396 [^] |
||
| Revision | 2023-09-19 11:01 by caristu | ||
| Description | With the fix for 0053411 the usage of the "net.bytebuddy.experimental" flag was added to the ant tasks that execute junit tests in order to avoid failures in the mockito tests when using JDK 22. It looks like this is can be fixed by upgrading to the latest bytebuddy library version. See[1]. [1] https://github.com/raphw/byte-buddy/issues/1396 [^] |
||
| Copyright © 2000 - 2009 MantisBT Group |
 |