I'll try to take a better look into this sometime this week. I'm pretty sure the JPA things should be good. I'll take a look at the unit tests for log4j-nosql a bit better to see if we can safely upgrade.
On 2 September 2014 09:24, Matt Sicker <[email protected]> wrote: > The JPA/EclipseLink update should be fine to test. There are a bunch of > tests involving JPA and HSQL or H2 (can't remember which). > > As to the NoSQL ones, other than integration testing, so far we can only > mock them. With something like Gora or Hazelcast or something more generic, > it's possible to use an in-memory data store. > > > On 2 September 2014 07:48, Gary Gregory <[email protected]> wrote: > >> Hi All and Nick: >> >> I see that these updates could be done: >> >> mongo-java-driver 2.12.3 <- 2.11.2 >> lightcouch 0.1.3 <- 0.0.6 >> org.eclipse.persistence.jpa 2.5.2 <- 2.5.1 >> >> But our unit tests do not seem very deep in NoSQL land. >> >> Can Nick or some else set up for better testing confirm that these >> updates are ok or not? >> >> Is there a 100% Java NoSQL provider that would be appropriate to use in >> our tests? >> >> Gary >> >> -- >> E-Mail: [email protected] | [email protected] >> Java Persistence with Hibernate, Second Edition >> <http://www.manning.com/bauer3/> >> JUnit in Action, Second Edition <http://www.manning.com/tahchiev/> >> Spring Batch in Action <http://www.manning.com/templier/> >> Blog: http://garygregory.wordpress.com >> Home: http://garygregory.com/ >> Tweet! http://twitter.com/GaryGregory >> > > > > -- > Matt Sicker <[email protected]> > -- Matt Sicker <[email protected]>
