Jetty 8 (and 7) are already end of life so we’re trying to figure out the
“best” way to get Jetty 9 support so we can get a camel-jetty component that
can use a supported version of Jetty. So for Camel 2.15, the question, to me,
is how to support both 8 and 9 (assuming we need to support 8 wh
As we don’t release camel components separately, I need to support the Jetty7,8
for very long time. It make sense that we can share the common logics in these
components to avoid the duplication.
Camel-http, camel-http4 share some common logic at the same time, maybe it’s
time for us to go thr
Github user oscerd closed the pull request at:
https://github.com/apache/camel/pull/354
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabl
On Tue, Dec 9, 2014 at 9:29 AM, Christian Schneider
wrote:
> Probably having two versions of camel-jetty is the only viable way then.
> I am a bit concerned about the code duplication though. The component it
> self is already quite big and the tests are even bigger. Should we try to
> move the co
Probably having two versions of camel-jetty is the only viable way then.
I am a bit concerned about the code duplication though. The component it
self is already quite big and the tests are even bigger. Should we try
to move the common things into a separate jar?
I think one deciding factor he
