Hi Okay the camel-box2 PR has been merged. So we can likely go ahead and remove the old one, and then rename the new from box2 to box.
On Sat, Mar 4, 2017 at 9:00 AM, 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 -- Claus Ibsen ----------------- http://davsclaus.com @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
