Hm, this is probably something we cannot control. The stack trace
points to the JLine library; maybe you can exclude this library?
On Tue, May 12, 2015 at 12:27 PM, jean-marc Mercier
>>> I've tried but didn't find out so far how to set it properly.<jeanmarc.mercier@gmail.com> wrote:
>
> Well I tried to add all JAR contained in the BaseX\lib in this windows. If I try to launch a XQUERY script with this running configuration, here is the result
>
> [ERROR] Terminal initialization failed; falling back to unsupported
> java.lang.NoClassDefFoundError: Could not initialize class org.fusesource.jansi.internal.Kernel32
> at org.fusesource.jansi.internal.WindowsSupport.getConsoleMode(WindowsSupport.java:50)
> at jline.WindowsTerminal.getConsoleMode(WindowsTerminal.java:204)
> at jline.WindowsTerminal.init(WindowsTerminal.java:82)
> at jline.TerminalFactory.create(TerminalFactory.java:101)
> at jline.TerminalFactory.get(TerminalFactory.java:158)
> at jline.console.ConsoleReader.<init>(ConsoleReader.java:229)
> at jline.console.ConsoleReader.<init>(ConsoleReader.java:221)
> at jline.console.ConsoleReader.<init>(ConsoleReader.java:209)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)
> at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)
> at java.lang.reflect.Constructor.newInstance(Unknown Source)
> at java.lang.Class.newInstance(Unknown Source)
> at org.basex.util.ConsoleReader$JLineConsoleReader.<init>(ConsoleReader.java:132)
> at org.basex.util.ConsoleReader.get(ConsoleReader.java:57)
> at org.basex.BaseX.console(BaseX.java:183)
> at org.basex.BaseX.<init>(BaseX.java:169)
> at org.basex.BaseX.main(BaseX.java:42)
>
>
> 2015-05-12 12:07 GMT+02:00 Christian Grün <christian.gruen@gmail.com>:
>>
>> Just a guess, but have you already tried to add all the additional BaseX libraries in this window (Add JARs...)?
>>
>>
>> On Tue, May 12, 2015 at 12:01 PM, jean-marc Mercier <jeanmarc.mercier@gmail.com> wrote:
>>>
>>> Christian,
>>>
>>> Hi. I confess that I don't know how to set a JAVA project running XQUERY with Basex interpreter under eclipse.
>>> I just know how to set an XQUERY project as pointed in http://docs.basex.org/wiki/Integrating_Eclipse.
>>>
>>> Maybe a possibility to avoid changing my whole project setting could be use an alternative Eclipse running Configuration ?
>>>
>>>
>>>
>>>
>>> 2015-05-12 11:31 GMT+02:00 Christian Grün <christian.gruen@gmail.com>:
>>>>
>>>> You may need to create a Java project and try it again. Please note that, from the Eclipse perspective, the XQuery processor of BaseX is a Java application.
>>>>
>>>>
>>>>
>>>> On Tue, May 12, 2015 at 11:28 AM, jean-marc Mercier <jeanmarc.mercier@gmail.com> wrote:
>>>>>
>>>>> Christian,
>>>>>
>>>>> Hello. Thx for your answer. I've tried your suggestion, but I can't set the Java Build path using Eclipse/ Project / Properties (my IDE is eclipse together with BaseX Interpreter) :
>>>>>
>>>>> This is a minor issue : I can survive using the BaseX server. It is only hardening dev / debug, since I don't know how to trace using BAseX server (fn:trace seems not to output anything using the basex server, maybe I missed something here ?).
>>>>>
>>>>> Cheers
>>>>>
>>>>>
>>>>> 2015-05-11 22:05 GMT+02:00 Christian Grün <christian.gruen@gmail.com>:
>>>>>>
>>>>>> Hi Jean-Marc,
>>>>>>
>>>>>> > I guess that it might be due to the fact that I don't know how to include
>>>>>> > multiple jar while using with eclipse. I tried to go to
>>>>>> > Windows/Preferences/XQUERY/Interpreters and set -classpath
>>>>>> > {BaseXDirectory}\lib\*, but it does not work.
>>>>>>
>>>>>> You will probably have to include the libraries as follows:
>>>>>>
>>>>>> Project → Properties → Java Build Path →
>>>>>> Libraries → Add JARs...
>>>>>>
>>>>>> Hope this helps,
>>>>>> Christian
>>>>>>
>>>>>>
>>>>>>
>>>>>> >
>>>>>> > Maybe somebody already met this small issue before ?
>>>>>> >
>>>>>> > Thanks for your answer,
>>>>>> >
>>>>>> > cheers
>>>>>
>>>>>
>>>>
>>>
>>
>