CGLib dependency should be shaded
envgap__awaitility__awaitility-55
01 / FAILURE SIGNATURE
As reported upstream
No identifying execution failure has been captured.
Not a benchmark task.
- In a clean container the reported failure did not reproduce, or the known fix did not make the project run.
02 / ENVIRONMENT RECIPE
- Base commit
de8ba227047b022a3f0a41123896f39540e263b4- Manifest
pom.xml- Reproduce
Awaiting issue-specific recipe- Run under trace
Awaiting a meaningful runtime command
03 / ORIGINAL ISSUE TEXT
awaitility/awaitility #55 · read the original issue
CGLib can be specially troublesome when you have different versions of the library that are being pulled by different libraries. It seems it's a common practice to shade this library (see Spring, Mockito) in order to avoid these problems. Can you consider this? Also, the version being used is almost 3 years old, it would be good to upgrade it (latest at this moment is 3.2.4)
04 / LABELS
Labels from the report text only; not yet run
No supported category has been assigned.
Label rules and the text that matched
[]