On Wed, 25 Apr 2007, Curt Arnold <[EMAIL PROTECTED]> wrote:
> Current run in progress did not have logging-log4j-component in its
> workspace despite the metadata looking okay.
Maybe this happened because I removed the directories in mid-run.
vmgump is taking more than nine hours for a single Gum
On Apr 24, 2007, at 1:39 PM, Stefan Bodewig wrote:
On Tue, 24 Apr 2007, Stefan Bodewig <[EMAIL PROTECTED]> wrote:
Which is a bug in the sync code IMHO.
Two sorts of bugs, ws-axis shows the other one.
I think we need to blow away the copy that Gump is working in, not
our checked out source
On Tue, 24 Apr 2007, Stefan Bodewig <[EMAIL PROTECTED]> wrote:
> Which is a bug in the sync code IMHO.
Two sorts of bugs, ws-axis shows the other one.
> I think we need to blow away the copy that Gump is working in, not
> our checked out source tree.
OK, I was wrong.
> vmgump and the Solaris z
On Mon, 23 Apr 2007, Curt Arnold <[EMAIL PROTECTED]> wrote:
> I inadvertently committed a symlink for a file in the logging-log4j-
> component project's SVN. I corrected it in rev 531339 committed
> late last night, but the subsequent Gump runs have had
> synchronization errors.
Which is a bug in
I inadvertently committed a symlink for a file in the logging-log4j-
component project's SVN. I corrected it in rev 531339 committed late
last night, but the subsequent Gump runs have had synchronization
errors. Could someone clear out the project working directory to
allow a fresh checkou
