Hi all,
the problem is clearly an incompatible version of jline (resulting of
the update we did in Karaf 4.1.x). It breaks other projects which are
using directly jline (for completer for instance).
So, the other projects should be refactored (camel, activemq, ...) to
not relay on jline but Karaf (for the completer for instance).
Anyway, it means that Karaf 4.1.0 is not yet ready to support any other
projects.
So, I'm going to 4.1.0-M1 first and we will invite maximum of people to
test on this milestone in order to clearly identify the breaking changes
and provide max backward compatibility when possible.
I already changed the version in Jira and I will cut 4.1.0-M1 later today.
Regards
JB
On 01/28/2017 03:32 PM, Jean-Baptiste Onofré wrote:
Hi guys,
as you might know, I'm preparing the Karaf 4.1.0 release.
We are mostly ok, but during my tests, I found that Camel (at least
2.18.1) commands are not available in the shell.
I suspect because they use the "old" style.
I also see lot of small annoying behaviors in the shell console (on
completion especially).
So, even we are mostly ready, I'm not sure it's fully ready for production.
Instead of directly releasing Karaf 4.1.0, I propose to release 4.1.0-M1
as a tech preview. I would allow people to review and test 4.1.0-M1 but
give a good message that's a tech preview.
WDYT ?
Regards
JB
On 01/05/2017 03:39 PM, Jean-Baptiste Onofré wrote:
Hi guys,
I started the updates and fixes for Karaf 4.1.0.
As dependencies, we will need Pax Exam 4.10.0 and Pax Web 6.0.1. Achim
and I will tackle this as it's pre-requisite for 4.1.0.
I plan to create karaf-4.1.x branch next week for a release the
following week.
Thoughts ?
Thanks,
Regards
JB
--
Jean-Baptiste Onofré
[email protected]
http://blog.nanthrax.net
Talend - http://www.talend.com
