I'm sorry for the regression issue. +1 for reverting the patch to avoid blocking the release. But we still find a way to address the cached bean issue, as the bean could be changed dynamically.
Willem Jiang Twitter: willemjiang Weibo: 姜宁willem On Tue, Jul 10, 2018 at 4:28 PM, Claus Ibsen <claus.ib...@gmail.com> wrote: > Hi > > I could not find a better solution so we reverted, but kept a similar > unit test with a regular bean (not impl processor). > > I think the branch is potentially ready for a release. > > On Tue, Jul 10, 2018 at 10:05 AM, Claus Ibsen <claus.ib...@gmail.com> > wrote: > > Hi > > > > I am taking a look and working on either an improved fix or going to > revert. > > The issue is that the bean in use is a bit "wrong" as it implements > > Processor which you should not really do. > > > > > > On Mon, Jul 9, 2018 at 10:10 AM, Andrea Cosentino > > <ancosen1...@yahoo.com.invalid> wrote: > >> I vote for reverting it for the moment and move to the next minor > release. > >> > >> -- > >> Andrea Cosentino > >> ---------------------------------- > >> Apache Camel PMC Chair > >> Apache Karaf Committer > >> Apache Servicemix PMC Member > >> Email: ancosen1...@yahoo.com > >> Twitter: @oscerd2 > >> Github: oscerd > >> > >> > >> > >> > >> > >> > >> On Monday, July 9, 2018, 10:08:39 AM GMT+2, Claus Ibsen < > claus.ib...@gmail.com> wrote: > >> > >> > >> > >> > >> > >> Hi > >> > >> We need to hold the release until we get this either reverted or find > >> out why it causes some existing unit tests to fail > >> https://issues.apache.org/jira/browse/CAMEL-12610 > >> > >> > >> > >> On Sun, Jul 8, 2018 at 9:58 PM, Gregor Zurowski > >> <gre...@list.zurowski.org> wrote: > >>> Hi, > >>> > >>> Unfortunately I was not able to cut the release due to the following > >>> problems with the Git repository when trying to push changes: > >>> > >>> remote: This repository has been locked due to synchronization issues: > >>> remote: - /x1/gitbox/broken/camel.txt exists due to a previous error, > >>> and prevents pushes. > >>> remote: This could either be a benign issue, or the repositories could > >>> be out of sync. > >>> remote: Please contact us...@infra.apache.org to have infrastructure > >>> resolve the issue. > >>> remote: > >>> To https://gitbox.apache.org/repos/asf/camel.git > >>> ! [remote rejected] release/2.21.2 -> release/2.21.2 (pre-receive > >>> hook declined) > >>> error: failed to push some refs to > >>> 'https://gitbox.apache.org/repos/asf/camel.git' > >>> > >>> Did anybody experience this in the past? > >>> > >>> Thanks in advance, > >>> Gregor > >>> > >>> > >>> On Tue, Jul 3, 2018 at 10:48 PM, Gregor Zurowski > >>> <gre...@list.zurowski.org> wrote: > >>>> Sure, I can take care of the release this weekend. > >>>> > >>>> Thanks, > >>>> Gregor > >>>> > >>>> > >>>> On Tue, Jul 3, 2018 at 1:09 PM, Claus Ibsen <claus.ib...@gmail.com> > wrote: > >>>>> Hi > >>>>> > >>>>> After the Camel 2.22.0 release, then I think we should work on > getting > >>>>> a new patch release out of the 2.21.x branch, eg 2.21.2. There are 38 > >>>>> JIRAs fixed for this version and we will get a couple of more which > >>>>> are pending to be backported. > >>>>> > >>>>> > >>>>> > >>>>> -- > >>>>> Claus Ibsen > >>>>> ----------------- > >>>>> http://davsclaus.com @davsclaus > >>>>> Camel in Action 2: https://www.manning.com/ibsen2 > >> > >> > >> > >> > >> -- > >> Claus Ibsen > >> ----------------- > >> http://davsclaus.com @davsclaus > >> Camel in Action 2: https://www.manning.com/ibsen2 > > > > > > > > -- > > Claus Ibsen > > ----------------- > > http://davsclaus.com @davsclaus > > Camel in Action 2: https://www.manning.com/ibsen2 > > > > -- > Claus Ibsen > ----------------- > http://davsclaus.com @davsclaus > Camel in Action 2: https://www.manning.com/ibsen2 >
