NoSuchField IGNORE_UNDEFINED
See original GitHub issueEvery time I try to run a junit test with @Rule annotation I’ve got java.lang.NoSuchFieldError: IGNORE_UNDEFINED Exception, I’ve also copied into my workspace your JUnit Example JUnitManaged.java as is and I’ve got the same problem. Wiremock version imported via maven is 2.5.1
<groupId>com.github.tomakehurst</groupId>
<artifactId>wiremock</artifactId>
<version>2.5.1</version>
</dependency>
Issue Analytics
- State:
- Created 7 years ago
- Comments:9
Top Results From Across the Web
NoSuchField IGNORE_UNDEFINED · Issue #605 · wiremock ...
Every time I try to run a junit test with @rule annotation I've got java.lang.NoSuchFieldError: IGNORE_UNDEFINED Exception, I've also copied ...
Read more >graalvm/native-image - Gitter
Any plan for making it possible to at least compile master without having to go through the whole process of getting a new...
Read more >NoSuchFieldError in Java - Baeldung
NoSuchFieldError extends the IncompatibleClassChangeError class and is thrown when the application tries to access or modify a field of an ...
Read more >java.lang.NoSuchFieldError exception while the field is defined
I'm working on a web application for Apache Tomcat. I'm using a class called Location in which i defined a field called ipAddresses....
Read more >Ansible Playbook - Task Was Never Completed ,No Results And Still ...
The ignoreerrors directive only works when the task is able to run and returns a value of 'failed'. It does not make Ansible...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
To solve this, I changed my pom to use the standalone instead:
I suggest you check what else is on your classpath as this is almost certainly a clashing dependency. Using the standalone artifact is a good workaround for this type of problem.