Gump's drive has always been to let people know of problems in the future (at least that's how I've always seen it). By compiling head of each project against each other, they discover when a problem is in the pipeline.
It seems that we should be able to freeze the version of Jaxen that Jelly uses in the gump descriptor and it'll stop complaining. Hen On 12/2/05, Paul Libbrecht <[EMAIL PROTECTED]> wrote: > Do i not understand Gump or the fact that we stick Jaxen head is > something that could be changed ? > Indeed, no-one really wishes to work with the latest jaxen currently. > > thanks > > paul > > Dion Gillard wrote: > > It's a break in how Jaxen works. > > Unless we upgrade all of Jelly to work with the code changes in Jaxen, the > > failures will continue. > > Personally, I'd rather stick where we are with jaxen in Jelly and stop Gump > > from nagging us. > > > > On 12/2/05, Henri Yandell <[EMAIL PROTECTED]> wrote: > > > >> These seem to have been going on for months. > >> > >> Any chance they can be fixed and stop spamming us? > >> > >> Hen > >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
