jpms: don't try to initialize mockito... about spring-boot HOT 2 CLOSED

this configuration could be skipped if the requirements aren't present

We're already doing that by checking for the presence of org.mockito.MockSettings. Beyond that, I don't think there's anything we can do here. There's no way for us to know with certainty if Mockito's being used and the problem should be shown as-is or, as is the case for you, Mockito isn't being used and it would be fine to swallow the exception.

I think this is another symptom of widespread support for the JPMS still being very much in its infancy in the Java ecosystem. Unfortunately, we don't think that Spring Boot is the right place to address problems with other libraries or the JPMS itself, particularly when doing so would result in worse diagnostics for the vast majority of our users who are not using the module system. From our perspective, this is a duplicate of mockito/mockito#2952.

from spring-boot.

yeah, I wasn't 100% certain if something could be done here. I hate to be this way but, better to report anyways IMHO.

I think this is another symptom of widespread support for the JPMS still being very much in its infancy in the Java ecosystem

absolutely, hopefully you aren't hating on me too much for reporting these things to try to move things out of infancy. Only gets there if we work towards it.

I've decided to take a stab at mockito/mockito#2604 which implemented I'd hope will fix mockito/mockito#2952

from spring-boot.