Hi I wonder if we shall deprecate more stuff on OSGi as its one of the most problematic platforms to support.
Ideally only OSGi Blueprint is the best supported we have. We should consider deprecating on OSGi - camel-scr - camel-cdi (use CDI outside OSGi like JEE, Weld/OpenWebBeans or anywhere else but OSGi) On Wed, Mar 1, 2017 at 9:33 AM, Claus Ibsen <claus.ib...@gmail.com> wrote: > Hi > > As part of CAMEL-10735: https://issues.apache.org/jira/browse/CAMEL-10735 > > We are deprecating code on 2.x that we anticipate to be removed in > Camel 3.0 onwards. > We have marked code as deprecated over the years, but recently got > more aggressive and deprecated more in camel-core. > > We have also marked components and other artifacts as deprecated, > which you can see in the overview on the readme file in github > https://github.com/apache/camel/blob/master/components/readme.adoc > > We have also decided to deprecate the Scala and Groovy DSL which will > be moved to camel-extra as their new home. Ticket about this: > https://issues.apache.org/jira/browse/CAMEL-10909 > > > For example camel-script allows to run python, php and some other > "exotic" languages. However these can be used as security attack > vectors when these libraries have issues. And because they are very > seldom used, we could maybe deprecate some of these languages and then > allow using javaScript (nashhorn from JDK) which should offer > sufficient scripting languge. And there is always groovy as well. > > We also think about deprecating components that wont support Java 9 or > are tricky to support there, for example jibx have some issues. > > > There are potential more to be deprecated, so we welcome any feedback > from the community. > > > > -- > 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
