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. D. On Fri, Mar 12, 2010 at 2:18 PM, Ethan Jewett <[email protected]> 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 > <[email protected]> wrote: > > See <http://hudson.zones.apache.org/hudson/job/ESME/changes> > > > > > > >
