That might be an even better option …

Kind regards,

        Peter Kriens

> On 27 okt. 2016, at 18:09, Richard S. Hall <[email protected]> wrote:
> 
> 
> On 10/27/16 12:03 , Peter Kriens wrote:
>> Neil Bartlett added JLine to the enRoute Gogo shell. Maybe this is causing 
>> the problem in your environment. You could add the standard Gogo shell to a 
>> repo and use that one.
> 
> The latest Gogo release also has JLine integration, although I think the 
> original Gogo Shell is available without JLine.
> 
> -> richard
> 
>> You could file a bug on OSGi enRoute bundles.
>> 
>> Kind regards,
>> 
>>      Peter Kriens
>> 
>> 
>>> On 27 okt. 2016, at 17:07, Liam O'Rourke <[email protected]> 
>>> <mailto:[email protected]> wrote:
>>> 
>>> Hello, I have been madly googling to no avail so I hope you can help.
>>> I have used enroute and bndtools 3.2 with the gogo shell successfully on 
>>> Windows 10. Having moved to enroute 2 and bndtools 3.3 when I add the 
>>> enroute.gogo.shell.provider to my run requirements the shell provider fails 
>>> with an UnsatisfiedLinkError and the message
>>> Could not load library. Reasons: [no jansi in java.library.path]
>>> I tried to get around this by taking a left over jansi-64-xxx file from 
>>> Karaf and copying that into the lib path and while this gets around the 
>>> error and gives me the shell the shell just takes return as a line feed and 
>>> doesn't send the input back to the shell. I can't see any changes in the 
>>> project commits that point to an obvious culprit here so any pointers would 
>>> be appreciated.
>>> Regards,
>>> Liam O'Rourke
>>> _______________________________________________
>>> OSGi Developer Mail List
>>> [email protected] <mailto:[email protected]>
>>> https://mail.osgi.org/mailman/listinfo/osgi-dev 
>>> <https://mail.osgi.org/mailman/listinfo/osgi-dev>
>> 
>> 
>> _______________________________________________
>> OSGi Developer Mail List
>> [email protected] <mailto:[email protected]>
>> https://mail.osgi.org/mailman/listinfo/osgi-dev 
>> <https://mail.osgi.org/mailman/listinfo/osgi-dev>
> _______________________________________________
> OSGi Developer Mail List
> [email protected] <mailto:[email protected]>
> https://mail.osgi.org/mailman/listinfo/osgi-dev 
> <https://mail.osgi.org/mailman/listinfo/osgi-dev>

Attachment: smime.p7s
Description: S/MIME cryptographic signature

_______________________________________________
OSGi Developer Mail List
[email protected]
https://mail.osgi.org/mailman/listinfo/osgi-dev

Reply via email to