esme-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Richard Hirsch <>
Subject Re: Hudson build is still unstable: ESME #151
Date Fri, 12 Mar 2010 16:41:58 GMT
I think the Hudson is problem is more of a timing problem rather than a
compass problem. Hudson always takes the trunk and the compass configuration
is correct there.

On Stax, it is a different problem. We can't use the default configuration
(based on files), because file access isn't allowed there. We are using a
JDBC-based search. I'll try and see what the problem is there.


On Fri, Mar 12, 2010 at 2:18 PM, Ethan Jewett <> wrote:

> Looks to me like this is because Compass search is broken again. It is
> broken on the Stax instance as well. I'm a little confused because it
> doesn't look like anything has really changed in the trunk for the
> last two weeks, but I'll try to take a look this weekend if no one
> else gets to it first.
> Ethan
> On Fri, Mar 12, 2010 at 6:19 AM, Apache Hudson Server
> <> wrote:
> > See <>
> >
> >
> >

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message