Hi, I noticed an interesting failure of HibernateCacheTest from the "hibernate-ehcache" module in a recent ORM CI build [1].
It failed to obtain hibernate-configuration-3.0.dtd from SourceForge (there was some service outage at SF at this time). Apart from the fact that the test uses the legacy URL (I'll fix that), I am wondering why the config parser tried to obtain the DTD remotely in the first place. We have LocalXmlResourceResolver in place which is there to prevent this. An indeed if I debug the test locally, I don't get to the place where it would download it from remote. Anyone with an idea why that would happen on CI? Thanks, --Gunnar [1] http://ci.hibernate.org/job/hibernate-orm-master-h2/988/testReport/junit/org.hibernate.test.cache/HibernateCacheTest/classMethod/ _______________________________________________ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
