When running IG and JPA together, IG fails to start with the following exception:
This happen because JPA is installing its own SLF4J binding, where IG expects LogBack to be installed.
Any application, using SLF4J and protected by JPA, can be subject to that kind of failures.
In the best case, application's logs would be redirected into the JPA log system, changing the usual places where an application administrator would expects its own application's logs.
In the worst case, this is like IG: init failure.