beehive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Julie Zhuo" <jz...@bea.com>
Subject RE: Beehive Check-in Test (Linux) Failed
Date Tue, 16 Aug 2005 21:58:49 GMT
FYI

I have reworked the script to get rid of the hard coded path to
dist.home. I am running it privately now and it seems working fine. I
will turn it alive after I make sure that this run is problem free.
Sorry it took so long.

Julie

-----Original Message-----
From: Julie Zhuo 
Sent: Tuesday, August 16, 2005 11:10 AM
To: Eddie ONeil; Beehive Developers
Cc: Alex Ramirez
Subject: RE: Beehive Check-in Test (Linux) Failed

I am taking look at this now. Will keep you updated.

Julie

-----Original Message-----
From: Eddie ONeil [mailto:ekoneil@gmail.com] 
Sent: Tuesday, August 16, 2005 10:45 AM
To: Beehive Developers
Cc: Alex Ramirez; Julie Zhuo
Subject: Re: Beehive Check-in Test (Linux) Failed

  One suggestion -- we've got a top-level target called
"run.test.dist" that can be invoked by:

  cd trunk/
  ant run.test.dist

which might avoid having to pass in the dist.home and beehive.version.
 Or is there a reason why CC needs the latter?

Eddie



On 8/16/05, Eddie ONeil <ekoneil@gmail.com> wrote:
> Alex and Julie--
> 
>   It appears that the Cruisecontrol box uses a hard-coded path to the
> distribution directory; this has now changed as of SVN 233004 from
> "apache-beehive-incubating-*" to "apache-beehive-*".
> 
>   Can someone adjust for this change on CC?
> 
> Thanks!
> 
> Eddie
> 
> 
> 
> On 8/16/05, jzhuo@bea.com <jzhuo@bea.com> wrote:
> > View results here ->
http://beehive01.bea.com/cruisecontrol/buildresults?log=log2005081608070
2
> >
>



Mime
View raw message