I've made a fix as https://svn.apache.org/r1665702 on trunk.
The impact of the change is solely to the automatic upgrader, and specifically only for the path that is currently causing the error (key/trust stores where the default type was previously being used in the config). -- Rob On 10 March 2015 at 22:17, Rob Godfrey <rob.j.godf...@gmail.com> wrote: > We have an error report from a user of the Java broker here: > https://issues.apache.org/jira/browse/QPID-6439 > > The fix will be trivial, but since it will mean anyone upgrading from > 0.30 or earlier to 0.32 will not be able to start their broker after > upgrading, I'd like to get a fix in for this. > > -- Rob > > On 10 March 2015 at 14:21, Justin Ross <justin.r...@gmail.com> wrote: >> Hi, folks. The 0.32 release candidate is now available. >> >> Release artifacts: https://dist.apache.org/repos/dist/dev/qpid/0.32-rc/ >> Maven staging repo: >> https://repository.apache.org/content/repositories/orgapacheqpid-1027 >> Test output: http://people.apache.org/~jross/qpid-0.32-rc.log >> >> This is pre-release code, for testing only! Thanks very much to those who >> have reported on their testing thus far. Please verify that the RC works >> for you. >> >> Note that the ssl_test failure in the cpp test output is a still unresolved >> problem with my test harness. The test succeeds when I run it manually. >> >> These release artifacts are signed. If approved by vote, the RC bits will >> be the GA bits. I will open the vote later today. >> >> Thanks! >> Justin >> >> --- >> 0.32 release page: >> https://cwiki.apache.org/confluence/display/qpid/0.32+Release --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
