hi claus, as per your previous heads up post,i mentioned i agreed to move deprecated apis to somewhere as dormant like luca already had suggested. however, this seems like an obvious deprecation, api will be turned off so the component will do so. for such cases, i agree your proposition. but for apis that will not be turned off and has activity but camel community may not be eager to maintain it, i agree with luca. we can keep them as dormant and maybe someone may want to paly with it.
cheers onder On Sat, 4 Mar 2017 at 08:01, Claus Ibsen <claus.ib...@gmail.com> wrote: > Hi > > There is a number of tickets for camel-box > https://issues.apache.org/jira/browse/CAMEL-9047 > https://issues.apache.org/jira/browse/CAMEL-10753 > https://issues.apache.org/jira/browse/CAMEL-10754 > https://issues.apache.org/jira/browse/CAMEL-10768 > > And the camel-box is using the old v1 api that is deprecated and will > be turned off in june 2017 > https://blogs.dropbox.com/developers/2016/06/api-v1-deprecated/ > > So we will eventually have a non working camel-box component soon. > > So I wonder if we PR for the camel-box2 component > https://github.com/apache/camel/pull/1505 > > If we should merge that PR, and then > - delete the old camel-box > - rename the new camel-box2 to camel-box > > As its based on the api component it should have fairly similar > options so users should not have so much of a problem migration. > > > > -- > Claus Ibsen > ----------------- > http://davsclaus.com @davsclaus > Camel in Action 2: https://www.manning.com/ibsen2 > -- Sent from my iPhone
