Hi Justin, I have another couple of changes I would like to request for inclusion in 0.20.
JIRA: https://issues.apache.org/jira/browse/QPID-4512 Commit: http://svn.us.apache.org/viewvc?view=revision&revision=1424757 Description: repairs deletion of messages via JMX such that the entire requested range can be actioned instead of just the first matching message. JIRA: https://issues.apache.org/jira/browse/QPID-4519 Commit: http://svn.us.apache.org/viewvc?view=revision&revision=1424763 Description: return the correct value for a hard coded boolean attribute, and stop checking the value from causing an update it shouldnt. Both changes are simple and extremely isolated within the JMX management plugin for the Java broker. Thanks, Robbie On 18 December 2012 22:49, Justin Ross <[email protected]> wrote: > Hi. Here's a new RC from revision 1423691. Note that it is *not* the > final RC. > > > http://people.apache.org/~**jross/qpid-0.20-rc3/<http://people.apache.org/~jross/qpid-0.20-rc3/> > > There've been just a handful of changes since RC2: > > r1418220 | rgodfrey | (Fri, 07 Dec 2012) | 2 lines > QPID-4454: Fixes to allow to/reply-to JMS type to be carried as > message annotations in AMQP 1.0 JMS client > > r1418544 | chug | (Fri, 07 Dec 2012) | 5 lines > NO-JIRA: repair build for VisualStudio 2010 > > r1421322 | robbie | (Thu, 13 Dec 2012) | 4 lines > QPID-4377: add missing licence headers to various files in the Java tree > > r1423679 | jross | (Tue, 18 Dec 2012) | 1 line > NO-JIRA: remove empty files from tree > > r1423691 | jross | (Tue, 18 Dec 2012) | 1 line > QPID-4377: Add missing license headers to JCA files > > Which of course is very good. I did, however, run into a problem trying > to address Gordon's issue regarding the C++ proton-based work. I made sure > that latest proton was installed, and further that pkg-config could find > it. I then created a new distribution. I looked for and couldn't find any > difference in the source distribution between RC2 and RC3, and it's > furthermore not clear to me why there would be. > > I then pushed on and attempted to run configure --with-proton, discovering > this problem: > > https://gist.github.com/**4332785 <https://gist.github.com/4332785> > > That looks like a dist issue, and I figure it's cropping up now because > this is the first time anyone's had a chance to test --with-proton. > > I think that needs to get fixed before we release 0.20, and so one more RC > will be required. > > Thanks! > Justin > > > ------------------------------**------------------------------**--------- > To unsubscribe, e-mail: > [email protected].**org<[email protected]> > For additional commands, e-mail: [email protected] > >
