Ok. Fixed in r898899. 

I did my dev and testing on 0.20 branch. I need to remember that
trunk is a lot different since 1433. 

   - Andy



----- Original Message ----
> From: Jean-Daniel Cryans <jdcry...@apache.org>
> To: hbase-dev@hadoop.apache.org
> Sent: Tue, January 12, 2010 7:23:37 PM
> Subject: Re: Build failed in Hudson: HBase-Patch #1067
> 
> It's an easy fix, hbase.root should be define in the contrib's
> build.xml (at least it fixed it for my replication contrib).
> 
> J-D
> 
> On Tue, Jan 12, 2010 at 11:35 AM, Apache Hudson Server
> wrote:
> > See 
> >
> > Changes:
> >
> > [apurtell] move all EC2 entries into New Features
> >
> > [apurtell] HBASE-2103 [EC2] pull version from build
> >
> > ------------------------------------------
> > Started by an SCM change
> > Started by an SCM change
> > Building remotely on vesta.apache.org (Ubuntu)
> > Updating https://svn.apache.org/repos/asf/hadoop/hbase/trunk
> > U         CHANGES.txt
> > U         src/contrib/ec2/bin/image/create-hbase-image-remote
> > U         src/contrib/ec2/bin/hbase-ec2-env.sh
> > A         src/contrib/ec2/build.xml
> > U         src/contrib/build-contrib.xml
> > At revision 898480
> > [locks-and-latches] Checking to see if we really have the locks
> > [locks-and-latches] Have all the locks, build can start
> > Buildfile: build.xml
> >
> > clean-contrib:
> >
> > clean:
> >
> > BUILD FAILED
> > 
> :544: 
> The following error occurred while executing this line:
> > 
> :63: 
> The following error occurred while executing this line:
> > 
> :2: 
> The following error occurred while executing this line:
> > 
> :73: 
> The following error occurred while executing this line:
> > 
> :5: 
> Source resource does not exist: 
> 
> >
> > Total time: 0 seconds
> > [locks-and-latches] Releasing all the locks
> > [locks-and-latches] All the locks released
> > Archiving artifacts
> > Recording test results
> > Publishing Clover coverage report...
> > Publishing Clover HTML report...
> > Publishing Clover XML report...
> > Publishing Clover coverage results...
> >
> >



      

Reply via email to