+1 for deprecating Http Client 3.1.
Willem Jiang Blog: http://willemjiang.blogspot.com (English) http://jnn.iteye.com (Chinese) Twitter: willemjiang Weibo: 姜宁willem On Sat, Mar 25, 2017 at 4:09 PM, Claus Ibsen <claus.ib...@gmail.com> wrote: > Hi > > We also have the old camel-http component that uses the Http Client > 3.1 that is EOL and has not been updated in many many years - in fact > its from August 2007. So lets get this deprecated as well before its > 10 years old ;) > http://search.maven.org/#search%7Cgav%7C1%7Cg%3A% > 22commons-httpclient%22%20AND%20a%3A%22commons-httpclient%22 > > On Thu, Mar 23, 2017 at 1:13 PM, Claus Ibsen <claus.ib...@gmail.com> > wrote: > > Hi > > > > There is also the old camel-servletlistener module which was intended > > for users on WAR files whom didnt want to use spring xml to bootstrap > > Camel. > > > > https://github.com/apache/camel/blob/master/components/ > camel-servletlistener/src/main/docs/servletlistener.adoc > > In today a modern WAR can deploy using a @WebListener where you can do > > your code to start / stop Camel. > > > > So I think we should deprecate this module as well. > > > > > > 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 > > > > -- > Claus Ibsen > ----------------- > http://davsclaus.com @davsclaus > Camel in Action 2: https://www.manning.com/ibsen2 >
