You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The reason is obvious - my app can't find Hamcrest classes in the classpath. It is rather confusing. Why do I need to keep a testing library in runtime? Of course, adding the next library helped me (pay attention to the scope):
The Hamcrest dependencies are required if you need to use the com.jcabi.http.mock classes
But I didn't use any mocks here. So why do I need Hamcrest then? Maybe it's better to create a separate HTTP response handler to avoid using hamcrest in runtime?
I tried to use
jcabi-github
library in order to get some statistics from repos and during the first run get the next exception:The reason is obvious - my app can't find
Hamcrest
classes in the classpath. It is rather confusing. Why do I need to keep a testing library in runtime? Of course, adding the next library helped me (pay attention to thescope
):But maybe it is better to fix the plugin to avoid usage of testing libraries in runtime?
The text was updated successfully, but these errors were encountered: