You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by Knut Anders Hatlen <Kn...@Sun.COM> on 2006/07/04 18:09:15 UTC
Debug code in the tar.gz files for 10.1.3.1?
Hi,
I was re-reading a log file from my testing of the second release
candidate when I discovered that the stack traces had line
numbers. I then looked at the size of derby.jar in some of the files
at http://people.apache.org/~fuzzylogic/10.1.3.1/:
db-derby-10.1.3.1-bin.zip - 2141382 bytes
db-derby-10.1.3.1-lib.tar.gz - 3113749 bytes
db-derby-10.1.3.1-bin.tar.gz - 3113749 bytes
db-derby-10.1.3.1-lib-debug.zip - 3113749 bytes
It seems like the tar.gz files contain the debug build. Does anybody
else see this?
--
Knut Anders
Re: Debug code in the tar.gz files for 10.1.3.1?
Posted by Andrew McIntyre <mc...@gmail.com>.
On 7/4/06, Knut Anders Hatlen <Kn...@sun.com> wrote:
>
> I was re-reading a log file from my testing of the second release
> candidate when I discovered that the stack traces had line
> numbers. I then looked at the size of derby.jar in some of the files
> at http://people.apache.org/~fuzzylogic/10.1.3.1/:
>
> db-derby-10.1.3.1-bin.zip - 2141382 bytes
> db-derby-10.1.3.1-lib.tar.gz - 3113749 bytes
> db-derby-10.1.3.1-bin.tar.gz - 3113749 bytes
> db-derby-10.1.3.1-lib-debug.zip - 3113749 bytes
>
> It seems like the tar.gz files contain the debug build. Does anybody
> else see this?
Ouch. I had regenerated the tar.gz's on the machine where I keep my
PGP key, which is a different machine than where I had built the jars.
I apparently unzipped the wrong version of the jars into my jars
directory when doing so.
Embarrassing, but easily fixed. I've updated the tar.gz to include the
proper build. A big thanks for catching that!
andrew