That is good news! I can take care of the upgrade but I wonder if we
should wait until derby 10.1.2.1 is available on ibiblio? Jeremy, do
you have an opinion?
Thanks,
--Kevin
Jim Marino wrote:
Hi,
Sorry about the delay. Upgrading to derby 10.1.2.1 works. I assume
we should rev to use that version. One thing I had to do was update
the das pom to point to that version of derby. Since that is not part
of my project area, would someone working on the das be prepared to
upgrade?
Jim
On Jan 20, 2006, at 3:10 PM, Kevin Williams wrote:
I cannot duplicate this problem on my OS X box (version 10.4.4). It
builds and runs fine.
Jim, will you have a chance to try Jeremy's suggestion?
Thanks,
--Kevin
Jeremy Boynes wrote:
Jim Marino wrote:
The problem was the issue Jeremy pointed to (http://
issues.apache.org/
jira/browse/DERBY-1). I ran into this problem on two separate OS
X machines. A workaround is to set the command line option -
Dderby.storage.fileSyncTransactionLog=true when running Maven.
Ideally,
we should have some conditional in the build script that puts
this in
for OS X. I would normally do this myself, but since it's not my
area
and I don't want to break the build, do someone more familiar
want to
do this?
Can you try with Derby 10.1.2.1 available from here:
http://db.apache.org/derby/releases/release-10.1.2.1.cgi
It's not on ibiblio yet so you will need to install the jar in your
local maven repo:
$ mvn install:install-file -Dpackaging=jar -
DgroupId=org.apache.derby \
-Dartifact=derby -Dversion=10.1.2.1 -Dfile=${file}
where ${file} is the derby.jar file from that download.
If that works it's simpler just to upgrade the Derby version. If not,
can you tell me the version of OSX and JRE so we can document that for
Derby.
Thanks
--
Jeremy
