On Tue, 2009-12-22 at 19:15 +0000, Robbie Gemmell wrote: > It is 1 character introduced 6 days ago iirc (I was on holiday and so didn't > start the broker again until yesterday) in the commit I mentioned. It > shouldn't be there (hence warnings from both my own pre-configuration check, > and log4j itself during configuration) and it hasn't been there in the years > that XML file has existed, but it is now. Currently the file is violating the > log4j XML DTD, once the character is removed it is not. I personally think > removing it is about as low risk as change gets (it's already removed and > tested on a branch if that helps put your mind at ease), and including it > will just make us look bad for not catching it during the release process, > considering it is plastered all over the broker startup output. >
Ok so I'll do a deal with you - if you'll commit to test the java release of 0.6. I'll let allow this change in the respin. How about that? Andrew BTW You should fix the wrap setting of your MUA --------------------------------------------------------------------- Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:[email protected]
