Tuesday, January 24, 2017

Oracle Maven Repository and Corrupted JARs

A colleague of mine approached me with a problem, I had recently switched a project over to Log4j2 and everything was going fine, but when he pull the latest develop branch and tried to build he got this eclipse error.

We tried a bunch of typical things, cleaning the build, deleting the project, doing a git clean, restarting Eclipse, etc. Decided to do a little Googling and found an article talking about corrupted JARs. So we though ok delete the folder for the JAR problem solved. Not so fast, happened again. So I thought a little more and asked him to open  the JAR file as if it was plain text. Low and behold we get some HTML.

The fix in this case was just that they needed to setup their authentication to the Oracle Maven Repo.



No comments: