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.
You could file a bug on OSGi enRoute bundles.
Kind regards,
Peter Kriens
> On 27 okt. 2016, at 17:07, Liam O'Rourke <l...@telensa.com> 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
> osgi-dev@mail.osgi.org
> https://mail.osgi.org/mailman/listinfo/osgi-dev
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ OSGi Developer Mail List osgi-dev@mail.osgi.org https://mail.osgi.org/mailman/listinfo/osgi-dev
