should be fixed, not link to openjpa actually
Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau 2014-06-04 0:11 GMT+02:00 Romain Manni-Bucau <[email protected]>: > Hi > > if we comment out org.apache.openejb.ClassLoaderUtil#getClosedJarFiles > then it passes but not sure what changed. We should fix it before the > release for sure. > > > > Romain Manni-Bucau > Twitter: @rmannibucau > Blog: http://rmannibucau.wordpress.com/ > LinkedIn: http://fr.linkedin.com/in/rmannibucau > Github: https://github.com/rmannibucau > > > 2014-06-03 21:55 GMT+02:00 jieryn <[email protected]>: > > I've recently started seeing a project failing because of unable to >> read the persistence.xml in a non-existant JAR file. This project >> works with 1.6.x lineage, but it breaks with the 1.7.x lineage. >> >> The reason is not apparent to me. This seems like a pretty huge >> regression... >> >> https://github.com/jieryn/javaee-example >> https://travis-ci.org/jieryn/javaee-example/builds/26695945 >> >> Check out, build with mvn clean install. Failure will be because of >> persistence.xml location failure. >> >> Please note, if I run with -Dtest= listing a single test class, it >> works as expected. So it seems there is some sort of static variable >> somewhere which is holding a reference to a previous arquillian jar or >> something along those lines.. >> >> Anyone know the problem here? This is blocking me. >> > >
