сен 15, 2023 2:15:40 PM org.aspectj.weaver.tools.Jdk14Trace error SEVERE:…
- User
сен 15, 2023 2:15:40 PM org.aspectj.weaver.tools.Jdk14Trace error SEVERE: org/apache/curator-test/shaded/com/google/common/io/Files100(URLClassLoader.java:74) at java.net.URLClassLoader1.run(URLClassLoader.java:363) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:362) at java.lang.ClassLoader.loadClass(ClassLoader.java:418) at sun.misc.LauncherConstructorSiteNoUnwrapNoCoerce.callConstructor(ConstructorSite.java:102) at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCallConstructor(CallSiteArray.java:57) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callConstructor(AbstractCallSite.java:232) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callConstructor(AbstractCallSite.java:236) at com.nexign.lbf.crab.scenarios.test.helpers.AbstractCompositeActionTest.initZoo(AbstractCompositeActionTest.groovy:60) at com.nexign.lbf.crab.scenarios.test.helpers.AbstractCompositeActionTest.commonTestSetUp(AbstractCompositeActionTest.groovy:129) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.junit.runners.model.FrameworkMethod1.evaluate(TestWatcher.java:55) at org.junit.rules.RunRules.evaluate(RunRules.java:20) at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57) at org.junit.runners.ParentRunner1.schedule(ParentRunner.java:71) at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) at org.junit.runners.ParentRunner.access2.evaluate(ParentRunner.java:268) at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27) at org.junit.runners.ParentRunner.run(ParentRunner.java:363) at org.junit.runner.JUnitCore.run(JUnitCore.java:137) at com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:69) at com.intellij.rt.junit.IdeaTestRunner1.execute(IdeaTestRunner.java:38) at com.intellij.rt.execution.junit.TestsRepeater.repeat(TestsRepeater.java:11) at com.intellij.rt.junit.IdeaTestRunner$Repeater.startRunnerWithArgs(IdeaTestRunner.java:35) at com.intellij.rt.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:232) at com.intellij.rt.junit.JUnitStarter.main(JUnitStarter.java:55)
- Assistant
This is an error message indicating that there is an issue with the aspectj-weaver library. The library is encountering an illegal state exception while trying to unpack a class signature.
The error specifically mentions that it was expecting ".", "<", or ";" but found "curatortest" instead while unpacking the signature of the class "org/apache/curator-test/shaded/com/google/common/collect/TreeTraverser<Ljava/io/File;>".
It seems that the aspectj-weaver library is trying to weave some aspects into the code, but is encountering a problem with the signature of a class from the "curator-test" package.
To resolve this issue, you can try the following steps:
- Ensure that you are using the correct version of the aspectj-weaver library that is compatible with your project.
- Check if there are any conflicting dependencies in your project that might be causing this issue. You can try updating or removing any conflicting dependencies.
- If you are using a build tool such as Maven or Gradle, try cleaning and rebuilding your project to ensure that all dependencies are properly resolved.
- If the issue persists, you may need to investigate further by checking the aspectj-weaver library documentation or seeking help from the library's support channels.
Note: This response assumes that you are encountering this error in a Java project using the aspectj-weaver library. If you are encountering this error in a different context or a different programming language, the solution might be different.