You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@karaf.apache.org by Aki Yoshida <el...@gmail.com> on 2014/08/07 14:45:22 UTC
karaf.shell.console 2.3.6 asking for jline 2.12
When I tried to use the latest camel-2.14-SNAPSHOT feature on
karaf-3.0.1 container, I noticed this problem. Camel feature has
recently switched from using karaf 2.3.5 to 2.3.6. And this new
karaf.shell.console is asking for jline 2.12, whereas karaf 3.0.1 has
jline 2.11.
http://camel.465427.n5.nabble.com/problem-with-current-2-14-SNAPSHOT-on-karaf-3-0-1-td5754840.html
Is the version range restriction set in karaf.shell.console for jline
intended, i.e., didn't want to set the range to [2.11,3)?
I see karaf-3.0.2-SNAPSHOT comes with jline 2.12. So there is no issue
with 3.0.2.
I am wondering if camel-2.14 should stay with karaf feature 2.3.5 or
just note that
a manual swapping of jline is required when using karaf 3.0.1.
I would appreciate your advice on this.
regards, aki
Re: karaf.shell.console 2.3.6 asking for jline 2.12
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Camel feature doesn't define the Karaf version (just the feature
namespace, compliant with multiple Karaf releases).
Moreover, I checked and the Camel feature doesn't define jline version.
The problem is not in the feature, it's in the Camel Karaf commands:
it's where a version range should be used.
Regards
JB
On 08/07/2014 06:27 PM, Aki Yoshida wrote:
> Hi JB,
>
> Thanks. But Camel extending its version range for Karaf itself won't
> help, as long as its camel feature uses Karaf feature 2.3.6, right?
> So you meant you would make Camel go back to use Karaf feature 2.3.5
> in its feature definition, no?
>
> regards, aki
>
> 2014-08-07 17:30 GMT+02:00 Jean-Baptiste Onofré <jb...@nanthrax.net>:
>> Hi Aki,
>>
>> Yes, IMHO, the jline 2.12 update has not been tested enough: this change the
>> Camel behavior, and the Karaf behavior on Windows7.
>>
>> Camel should extend the version range for Karaf (and dependencies).
>> I will do that.
>>
>> Regards
>> JB
>>
>> On 08/07/2014 02:45 PM, Aki Yoshida wrote:
>>>
>>> When I tried to use the latest camel-2.14-SNAPSHOT feature on
>>> karaf-3.0.1 container, I noticed this problem. Camel feature has
>>> recently switched from using karaf 2.3.5 to 2.3.6. And this new
>>> karaf.shell.console is asking for jline 2.12, whereas karaf 3.0.1 has
>>> jline 2.11.
>>>
>>>
>>> http://camel.465427.n5.nabble.com/problem-with-current-2-14-SNAPSHOT-on-karaf-3-0-1-td5754840.html
>>>
>>> Is the version range restriction set in karaf.shell.console for jline
>>> intended, i.e., didn't want to set the range to [2.11,3)?
>>>
>>> I see karaf-3.0.2-SNAPSHOT comes with jline 2.12. So there is no issue
>>> with 3.0.2.
>>>
>>> I am wondering if camel-2.14 should stay with karaf feature 2.3.5 or
>>> just note that
>>> a manual swapping of jline is required when using karaf 3.0.1.
>>>
>>> I would appreciate your advice on this.
>>>
>>> regards, aki
>>>
>>
>> --
>> Jean-Baptiste Onofré
>> jbonofre@apache.org
>> http://blog.nanthrax.net
>> Talend - http://www.talend.com
--
Jean-Baptiste Onofré
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
Re: karaf.shell.console 2.3.6 asking for jline 2.12
Posted by Aki Yoshida <el...@gmail.com>.
Hi JB,
Thanks. But Camel extending its version range for Karaf itself won't
help, as long as its camel feature uses Karaf feature 2.3.6, right?
So you meant you would make Camel go back to use Karaf feature 2.3.5
in its feature definition, no?
regards, aki
2014-08-07 17:30 GMT+02:00 Jean-Baptiste Onofré <jb...@nanthrax.net>:
> Hi Aki,
>
> Yes, IMHO, the jline 2.12 update has not been tested enough: this change the
> Camel behavior, and the Karaf behavior on Windows7.
>
> Camel should extend the version range for Karaf (and dependencies).
> I will do that.
>
> Regards
> JB
>
> On 08/07/2014 02:45 PM, Aki Yoshida wrote:
>>
>> When I tried to use the latest camel-2.14-SNAPSHOT feature on
>> karaf-3.0.1 container, I noticed this problem. Camel feature has
>> recently switched from using karaf 2.3.5 to 2.3.6. And this new
>> karaf.shell.console is asking for jline 2.12, whereas karaf 3.0.1 has
>> jline 2.11.
>>
>>
>> http://camel.465427.n5.nabble.com/problem-with-current-2-14-SNAPSHOT-on-karaf-3-0-1-td5754840.html
>>
>> Is the version range restriction set in karaf.shell.console for jline
>> intended, i.e., didn't want to set the range to [2.11,3)?
>>
>> I see karaf-3.0.2-SNAPSHOT comes with jline 2.12. So there is no issue
>> with 3.0.2.
>>
>> I am wondering if camel-2.14 should stay with karaf feature 2.3.5 or
>> just note that
>> a manual swapping of jline is required when using karaf 3.0.1.
>>
>> I would appreciate your advice on this.
>>
>> regards, aki
>>
>
> --
> Jean-Baptiste Onofré
> jbonofre@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
Re: karaf.shell.console 2.3.6 asking for jline 2.12
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Hi Aki,
Yes, IMHO, the jline 2.12 update has not been tested enough: this change
the Camel behavior, and the Karaf behavior on Windows7.
Camel should extend the version range for Karaf (and dependencies).
I will do that.
Regards
JB
On 08/07/2014 02:45 PM, Aki Yoshida wrote:
> When I tried to use the latest camel-2.14-SNAPSHOT feature on
> karaf-3.0.1 container, I noticed this problem. Camel feature has
> recently switched from using karaf 2.3.5 to 2.3.6. And this new
> karaf.shell.console is asking for jline 2.12, whereas karaf 3.0.1 has
> jline 2.11.
>
> http://camel.465427.n5.nabble.com/problem-with-current-2-14-SNAPSHOT-on-karaf-3-0-1-td5754840.html
>
> Is the version range restriction set in karaf.shell.console for jline
> intended, i.e., didn't want to set the range to [2.11,3)?
>
> I see karaf-3.0.2-SNAPSHOT comes with jline 2.12. So there is no issue
> with 3.0.2.
>
> I am wondering if camel-2.14 should stay with karaf feature 2.3.5 or
> just note that
> a manual swapping of jline is required when using karaf 3.0.1.
>
> I would appreciate your advice on this.
>
> regards, aki
>
--
Jean-Baptiste Onofré
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com