gump-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bill Barker" <>
Subject RE: Failure in derby-split-1
Date Sat, 18 Feb 2006 00:06:28 GMT

> -----Original Message-----
> From: Andrew McIntyre [] 
> Sent: Friday, February 17, 2006 3:22 PM
> To: Gump code and data
> Subject: Failure in derby-split-1
> Just noticed this has been failing for a while.
> The failure is here:
>  compile_reference:
>    [javac] Compiling 10 source files to
> /x1/gump/public/workspace/db-derby/classes
>    [javac]  
> /x1/gump/public/workspace/db-derby/java/engine/org/apache/derb
>  package org.apache.derby.shared.common.reference does not exist
>    [javac]     org.apache.derby.shared.common.reference.SQLState
>    [javac]                                             ^
>    [javac] 1 error
> This looks like svn did not properly update some files. The file that
> is missing exists in the source tree here:
> d/org/apache/derby/shared/common/reference/
> Maybe those new files didn't update properly? Perhaps the pointers to
> the various source directories in tools/ant/properties/
> didn't update? Maybe there's something in the metadata I need to
> change to find the new files?
> Not sure what's going on, but I'll be glad to help if someone could
> take a look and make sure that the new files in java/shared are there.

I can't check the files myself, but it's hard to believe that 'svn up' has
been failing for this long.

What I'd check is if 'ant gump_split_1' works.  It's likely that the missing
file simply needs to be added to what that target builds.

> Thanks!
> andrew
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

This message is intended only for the use of the person(s) listed above as the intended recipient(s),
and may contain information that is PRIVILEGED and CONFIDENTIAL.  If you are not an intended
recipient, you may not read, copy, or distribute this message or any attachment. If you received
this communication in error, please notify us immediately by e-mail and then delete all copies
of this message and any attachments.

In addition you should be aware that ordinary (unencrypted) e-mail sent through the Internet
is not secure. Do not send confidential or sensitive information, such as social security
numbers, account numbers, personal identification numbers and passwords, to us via ordinary
(unencrypted) e-mail.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message