I was able to diagnose this problem by looking at the metadata files that maven keep in:
cat ~/.m2/repository/path-to-your-dependency/maven-metadata-<remote-hostname>.xml
Personal Log of Vicente "Thirdy" S. de Rivera III. Thoughts and opinions about everyday life, Programming, Music etc.
I was able to diagnose this problem by looking at the metadata files that maven keep in:
cat ~/.m2/repository/path-to-your-dependency/maven-metadata-<remote-hostname>.xml
Today I was writing a class JUnit test code that of course runs very slow as it starts up by bringing the whole AWS infrastructure online (exaggeration) just to run several assertTrue statements..
As you might suspect, I am not fond of writing this test code. This is because I know in my heart that this test code will be more burden than useful:
PS: The title is inspired by Nico Rosberg's podcast called "Beyond Victory"
While investigating an issue, I saw a NullPointerException without a stacktrace..
ERROR logs that omits the throwable object (and it is available) is quite devastating. I call such situation 'swallowing the exception'.
However, this time, it is very different. Apparently the HotSpot JVM may opt to not log the stacktrace but only the exception: