I have made occasional tries at using BaseX for my project over the years. After a longer pause I am trying again. I downloaded the latest version (9.1.3). If I try to start BaseX from the command line it starts a version 7.9 and asks we if I want to update. Can someone please explain what is going on?
Philip
Hi Philip,
probably another (old) BaseX version is still installed and executed. What OS do you use? And what is the exact command on the command line you use to start BaseX? Maybe your PATH is still pointing to the old version.
Cheers, Alex
On 6. Jan 2020, at 05:49, Philip Spaelti spaelti@gmail.com wrote:
I have made occasional tries at using BaseX for my project over the years. After a longer pause I am trying again. I downloaded the latest version (9.1.3). If I try to start BaseX from the command line it starts a version 7.9 and asks we if I want to update. Can someone please explain what is going on?
Philip
Hi Alex, Thank you. I’m on Mac OS 10.15
Being somewhat aware of this issue, I thought I had removed all old versions and had even tried to set the PATH to point to my basex folder. I now realized that I had another version of BaseX installed in /usr/local/Cellar. And after removing that version, the “basexgui” command no longer works (unless I am in the basex folder). So my attempt at setting the PATH was not successful. I guess I’ll have to try to work out how to set the PATH variable to point to the right thing.
Philip
On Mon, Jan 6, 2020 at 5:04 PM Alexander Holupirek alex@holupirek.de wrote:
Hi Philip,
probably another (old) BaseX version is still installed and executed. What OS do you use? And what is the exact command on the command line you use to start BaseX? Maybe your PATH is still pointing to the old version.
Cheers, Alex
On 6. Jan 2020, at 05:49, Philip Spaelti spaelti@gmail.com wrote:
I have made occasional tries at using BaseX for my project over the
years. After a longer pause I am trying again. I downloaded the latest version (9.1.3). If I try to start BaseX from the command line it starts a version 7.9 and asks we if I want to update. Can someone please explain what is going on?
Philip
Hi Philip,
on MacOs you can use homebrew [1] for a convenient way to install basex 9.3.1
Using the .zip release of BaseX you have to make sure to invoke the startup scripts explicitely. For instance:
$ cd /tmp $ wget http://files.basex.org/releases/9.3.1/BaseX931.zip $ unzip BaseX931.zip $ cd basex $ pwd /tmp/basex $ ./bin/basexhttp /private/tmp/basex/.basex: writing new configuration file. BaseX 9.3.1 [HTTP Server] [main] INFO org.eclipse.jetty.util.log - Logging initialized @229ms to org.eclipse.jetty.util.log.Slf4jLog [main] INFO org.eclipse.jetty.server.Server - jetty-9.4.24.v20191120; built: 2019-11-20T21:37:49.771Z; git: 363d5f2df3a8a28de40604320230664b9c793c16; jvm 11.0.1+13-LTS [main] INFO org.eclipse.jetty.webapp.StandardDescriptorProcessor - NO JSP Support for /, did not find org.eclipse.jetty.jsp.JettyJspServlet [main] INFO org.eclipse.jetty.server.session - DefaultSessionIdManager workerName=node0 [main] INFO org.eclipse.jetty.server.session - No SessionScavenger set, using defaults [main] INFO org.eclipse.jetty.server.session - node0 Scavenging every 600000ms Server was started (port: 1984). [main] INFO org.eclipse.jetty.server.handler.ContextHandler - Started o.e.j.w.WebAppContext@72c8e7b{BaseX: The XML Database and XQuery Processor,/,file:///private/tmp/basex/webapp/,AVAILABLE}{/private/tmp/basex/webapp} [main] INFO org.eclipse.jetty.server.AbstractConnector - Started ServerConnector@57a3af25{HTTP/1.1,[http/1.1]}{0.0.0.0:8984} [main] INFO org.eclipse.jetty.server.Server - Started @526ms HTTP STOP Server was started (port: 8985). HTTP Server was started (port: 8984).
Hope this helps, Alex
[1] https://brew.sh
On 7. Jan 2020, at 03:17, Philip Spaelti spaelti@gmail.com wrote:
Hi Alex, Thank you. I’m on Mac OS 10.15
Being somewhat aware of this issue, I thought I had removed all old versions and had even tried to set the PATH to point to my basex folder. I now realized that I had another version of BaseX installed in /usr/local/Cellar. And after removing that version, the “basexgui” command no longer works (unless I am in the basex folder). So my attempt at setting the PATH was not successful. I guess I’ll have to try to work out how to set the PATH variable to point to the right thing.
Philip
On Mon, Jan 6, 2020 at 5:04 PM Alexander Holupirek alex@holupirek.de wrote: Hi Philip,
probably another (old) BaseX version is still installed and executed. What OS do you use? And what is the exact command on the command line you use to start BaseX? Maybe your PATH is still pointing to the old version.
Cheers, Alex
On 6. Jan 2020, at 05:49, Philip Spaelti spaelti@gmail.com wrote:
I have made occasional tries at using BaseX for my project over the years. After a longer pause I am trying again. I downloaded the latest version (9.1.3). If I try to start BaseX from the command line it starts a version 7.9 and asks we if I want to update. Can someone please explain what is going on?
Philip
basex-talk@mailman.uni-konstanz.de
-
Alexander Holupirek -
Philip Spaelti