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 ma
Hi
I propose to deprecate camel-guice. That module has never really been
in much use / attention / maintained. And over the years guice has
been pain to support / guice itself was in trouble when the leaders
left and google didnt do any releases and whatnot.
On Wed, Mar 1, 2017 at 9:33 AM, Clau
+1
btw, should we have a sort of "camel dormant" repository were we can
put stuffs that are not actively maintained ?
---
Luca Burgazzoli
On Fri, Mar 3, 2017 at 2:30 PM, Claus Ibsen wrote:
> Hi
>
> I propose to deprecate camel-guice. That module has never really been
> in much use / attention
+1 for luca.
as some commercial companies ( i know we have many in my country ) prefer
to move to next version of java as they get more mature. so some apis and
components may be actibely maintained with specific version but i propose
to keep them as dormant maybe somebody like devs in my country
Hi
Okay so some of the scripting languages and other languages that are
EOL and has not been released in many many years are being deprecated
now
https://issues.apache.org/jira/browse/CAMEL-10973
On Wed, Mar 1, 2017 at 9:33 AM, Claus Ibsen wrote:
> Hi
>
> As part of CAMEL-10735: https://issues.a
On Sat, Mar 4, 2017 at 9:51 PM, Onder SEZGIN wrote:
> +1 for luca.
>
> as some commercial companies ( i know we have many in my country ) prefer
> to move to next version of java as they get more mature. so some apis and
> components may be actibely maintained with specific version but i propose
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
+1
---
Luca Burgazzoli
On Thu, Mar 16, 2017 at 8:16 PM, Claus Ibsen wrote:
> 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
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 us
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
+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 wrote:
> Hi
>
> We also have the old camel-http component that uses th
11 matches
Mail list logo
