Thanks, I'll stick with the old gogo shell for now and raise a bug. Regards, Liam O'Rourke
On 27 October 2016 at 17:21, <osgi-dev-requ...@mail.osgi.org> wrote: > Send osgi-dev mailing list submissions to > osgi-dev@mail.osgi.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://mail.osgi.org/mailman/listinfo/osgi-dev > or, via email, send a message with subject or body 'help' to > osgi-dev-requ...@mail.osgi.org > > You can reach the person managing the list at > osgi-dev-ow...@mail.osgi.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of osgi-dev digest..." > > Today's Topics: > > 1. Re: Enroute 2 gogo shell provider on windows (Peter Kriens) > 2. Re: Enroute 2 gogo shell provider on windows (Richard S. Hall) > 3. Re: Enroute 2 gogo shell provider on windows (Peter Kriens) > > > ---------- Forwarded message ---------- > From: Peter Kriens <peter.kri...@aqute.biz> > To: OSGi Developer Mail List <osgi-dev@mail.osgi.org> > Cc: > Date: Thu, 27 Oct 2016 18:03:31 +0200 > Subject: Re: [osgi-dev] Enroute 2 gogo shell provider on windows > 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 > > > > ---------- Forwarded message ---------- > From: "Richard S. Hall" <he...@ungoverned.org> > To: OSGi Developer Mail List <osgi-dev@mail.osgi.org> > Cc: > Date: Thu, 27 Oct 2016 12:09:42 -0400 > Subject: Re: [osgi-dev] Enroute 2 gogo shell provider on windows > > 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 <l...@telensa.com> > <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 > listosgi-...@mail.osgi.orghttps://mail.osgi.org/mailman/listinfo/osgi-dev > > > > _______________________________________________ > OSGi Developer Mail > listosgi-...@mail.osgi.orghttps://mail.osgi.org/mailman/listinfo/osgi-dev > > > > > ---------- Forwarded message ---------- > From: Peter Kriens <peter.kri...@aqute.biz> > To: OSGi Developer Mail List <osgi-dev@mail.osgi.org> > Cc: > Date: Thu, 27 Oct 2016 18:21:14 +0200 > Subject: Re: [osgi-dev] Enroute 2 gogo shell provider on windows > That might be an even better option … > > Kind regards, > > Peter Kriens > > On 27 okt. 2016, at 18:09, Richard S. Hall <he...@ungoverned.org> 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 <l...@telensa.com> > <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 > listosgi-...@mail.osgi.orghttps://mail.osgi.org/mailman/listinfo/osgi-dev > > > > _______________________________________________ > OSGi Developer Mail > listosgi-...@mail.osgi.orghttps://mail.osgi.org/mailman/listinfo/osgi-dev > > > _______________________________________________ > OSGi Developer Mail List > osgi-dev@mail.osgi.org > https://mail.osgi.org/mailman/listinfo/osgi-dev > > > > _______________________________________________ > OSGi Developer Mail List > osgi-dev@mail.osgi.org > https://mail.osgi.org/mailman/listinfo/osgi-dev >
_______________________________________________ OSGi Developer Mail List osgi-dev@mail.osgi.org https://mail.osgi.org/mailman/listinfo/osgi-dev
