-
Component Upgrade
-
Resolution: Done
-
Major
-
None
-
None
Upgrade to latest Berkeley DB version. This is currently 5.0.34.
[ISPN-1863] Upgrade Berkeley DB version to 5.x
Ove Ranheim (Inactive)
added a comment - Nice 
Galder Zamarreño
added a comment - Done now: http://repository.jboss.org/nexus/content/groups/public/com/sleepycat/je/5.0.34/je-5.0.34.pom 
Galder Zamarreño
added a comment - Done now: http://repository.jboss.org/nexus/content/groups/public/com/sleepycat/je/5.0.34/je-5.0.34.pom Galder Zamarreño
added a comment - Yes it is cos you never know who's gonna need that pom and if we get intermittent failures, it doesn't look good on us, since we're the ones depending on it. This decision has been the result of countless emails to our IT department complaining about it. It has an easy fix though.
Galder Zamarreño
added a comment - Yes it is cos you never know who's gonna need that pom and if we get intermittent failures, it doesn't look good on us, since we're the ones depending on it. This decision has been the result of countless emails to our IT department complaining about it. It has an easy fix though. Ove Ranheim (Inactive)
added a comment - Does it really matter if (http://download.oracle.com/maven/com/sleepycat/je/5.0.34/je-5.0.34.pom) is unstable, because when nexus has fetched the artifact, you already have a copy in your repo.
Ove Ranheim (Inactive)
added a comment - Does it really matter if ( http://download.oracle.com/maven/com/sleepycat/je/5.0.34/je-5.0.34.pom ) is unstable, because when nexus has fetched the artifact, you already have a copy in your repo. Galder Zamarreño
added a comment - We no longer proxy to the Oracle maven repo cos it's not reliable and it would often stop responding. So, as a result of this, we need to upload the jars manually to our thirdparty nexus repo.
Galder Zamarreño
added a comment - We no longer proxy to the Oracle maven repo cos it's not reliable and it would often stop responding. So, as a result of this, we need to upload the jars manually to our thirdparty nexus repo. Galder Zamarreño
added a comment - Hmmm, something's not right with Nexus proxying cos I'm getting:
[ERROR] Failed to execute goal on project infinispan-cachestore-bdbje: Could not resolve dependencies for project org.infinispan:infinispan-cachestore-bdbje:bundle:5.2.0-SNAPSHOT: Failure to find com.sleepycat:je:jar:5.0.34...
I'll check with Paul Gier.
Galder Zamarreño
added a comment - Hmmm, something's not right with Nexus proxying cos I'm getting:
[ERROR] Failed to execute goal on project infinispan-cachestore-bdbje: Could not resolve dependencies for project org.infinispan:infinispan-cachestore-bdbje:bundle:5.2.0-SNAPSHOT: Failure to find com.sleepycat:je:jar:5.0.34...
I'll check with Paul Gier. Ove Ranheim (Inactive)
added a comment - I also kept the 00000000.jdb files from 4.0.92 and replaced the bdbje module jar with 5.0.34. It seems to be backwards compatible too. No errors and everything looks fine.
Ove Ranheim (Inactive)
added a comment - I also kept the 00000000.jdb files from 4.0.92 and replaced the bdbje module jar with 5.0.34. It seems to be backwards compatible too. No errors and everything looks fine. Did a local test and updated parent/pom.xml for version.bdbje to 5.0.34. TestSuite runs successfully
Ove Ranheim (Inactive)
added a comment - - edited Did a local test and updated parent/pom.xml for version.bdbje to 5.0.34. TestSuite runs successfully 
Pom is up but jars are not, so this needs fixing.