Determine remote server version.
Hi all,
I'm trying to determine the BaseX version running a remote server.
When I connect using the client on my local machine the server does not say which version it is
When I use the GUI to connect to the remote server I can't find any info on the version.
When I login to the remote machine and go to the server folder I can't find any info on which version it is.
When I look at the logs in the .logs folder I can't find any info on the server version (I could not find the startup info that the server generates).
I copied the BaseX.jar to a place where I could unpack it and found version "6.6" in the META-INF/maven/org.basex/basex/pom.xml file.
Is there a more convenient way of determining the remote version that I missed? And did I actually find the correct version in the pom?
Hartelijke groet,
Huib Verweij.
P.S. In the BaseX GUI the "Logs" tab shows me the logs of the local BaseX even when I connect to a remote BaseX - could be on puprpose, I just found it somewhat counter intuitive.
Quoted text · Huib Verwey · 1 line
> I'm trying to determine the BaseX version running a remote server.
…true, that's not possible right now. Which solution would you prefer?
Quoted text · Huib Verwey · 1 line
> P.S. In the BaseX GUI the "Logs" tab shows me the logs of the local BaseX even when I connect to a remote BaseX - could be on puprpose, I just found it somewhat counter intuitive.
…true; I've just changed the wording to "Local Logs".
Christian
Quoted text · Huib Verwey · 22 lines
> When I connect using the client on my local machine the server does not say which version it is > > When I use the GUI to connect to the remote server I can't find any info on the version. > > When I login to the remote machine and go to the server folder I can't find any info on which version it is. > > When I look at the logs in the .logs folder I can't find any info on the server version (I could not find the startup info that the server generates). > > I copied the BaseX.jar to a place where I could unpack it and found version "6.6" in the META-INF/maven/org.basex/basex/pom.xml file. > > Is there a more convenient way of determining the remote version that I missed? And did I actually find the correct version in the pom? > > Hartelijke groet, > > Huib Verweij. > > P.S. In the BaseX GUI the "Logs" tab shows me the logs of the local BaseX even when I connect to a remote BaseX - could be on puprpose, I just found it somewhat counter intuitive. > _______________________________________________ > BaseX-Talk mailing list > BaseX-Talk at mailman.uni-konstanz.de > https://mailman.uni-konstanz.de/mailman/listinfo/basex-talk >
What about adding version information to db:system() and another function db:version() to be able to retrieve version information in an xquery-processable manner?
Quoted text · Christian Grün · 38 lines
Am 18.05.11 17:58, schrieb Christian Grün: >> I'm trying to determine the BaseX version running a remote server. > > …true, that's not possible right now. Which solution would you prefer? > >> P.S. In the BaseX GUI the "Logs" tab shows me the logs of the local BaseX even when I connect to a remote BaseX - could be on puprpose, I just found it somewhat counter intuitive. > > …true; I've just changed the wording to "Local Logs". > > Christian > > >> When I connect using the client on my local machine the server does not say which version it is >> >> When I use the GUI to connect to the remote server I can't find any info on the version. >> >> When I login to the remote machine and go to the server folder I can't find any info on which version it is. >> >> When I look at the logs in the .logs folder I can't find any info on the server version (I could not find the startup info that the server generates). >> >> I copied the BaseX.jar to a place where I could unpack it and found version "6.6" in the META-INF/maven/org.basex/basex/pom.xml file. >> >> Is there a more convenient way of determining the remote version that I missed? And did I actually find the correct version in the pom? >> >> Hartelijke groet, >> >> Huib Verweij. >> >> P.S. In the BaseX GUI the "Logs" tab shows me the logs of the local BaseX even when I connect to a remote BaseX - could be on puprpose, I just found it somewhat counter intuitive. >> _______________________________________________ >> BaseX-Talk mailing list >> BaseX-Talk at mailman.uni-konstanz.de >> https://mailman.uni-konstanz.de/mailman/listinfo/basex-talk >> > _______________________________________________ > BaseX-Talk mailing list > BaseX-Talk at mailman.uni-konstanz.de > https://mailman.uni-konstanz.de/mailman/listinfo/basex-talk
I would expect version information as part of INFO command output.
Jan
2011/5/19 Jens Erat <jens.erat at uni-konstanz.de>
Quoted text · Jens Erat · 72 lines
> What about adding version information to db:system() and another > function db:version() to be able to retrieve version information in an > xquery-processable manner? > > -- > Jens Erat > > [phone]: tel:+49-151-56961126 > [mail]: mailto:email at jenserat.de > [jabber]: xmpp:jabber at jenserat.de > [web]: http://www.jenserat.de > > PGP: 350E D9B6 9ADC 2DED F5F2 8549 CBC2 613C D745 722B > OTR: AA2C 0B55 F8D5 CEED 8F4F 6EE1 1EBF DD62 5426 7899 > > Am 18.05.11 17:58, schrieb Christian Grün: > >> I'm trying to determine the BaseX version running a remote server. > > > > …true, that's not possible right now. Which solution would you prefer? > > > >> P.S. In the BaseX GUI the "Logs" tab shows me the logs of the local > BaseX even when I connect to a remote BaseX - could be on puprpose, I just > found it somewhat counter intuitive. > > > > …true; I've just changed the wording to "Local Logs". > > > > Christian > > > > > >> When I connect using the client on my local machine the server does not > say which version it is > >> > >> When I use the GUI to connect to the remote server I can't find any info > on the version. > >> > >> When I login to the remote machine and go to the server folder I can't > find any info on which version it is. > >> > >> When I look at the logs in the .logs folder I can't find any info on the > server version (I could not find the startup info that the server > generates). > >> > >> I copied the BaseX.jar to a place where I could unpack it and found > version "6.6" in the META-INF/maven/org.basex/basex/pom.xml file. > >> > >> Is there a more convenient way of determining the remote version that I > missed? And did I actually find the correct version in the pom? > >> > >> Hartelijke groet, > >> > >> Huib Verweij. > >> > >> P.S. In the BaseX GUI the "Logs" tab shows me the logs of the local > BaseX even when I connect to a remote BaseX - could be on puprpose, I just > found it somewhat counter intuitive. > >> _______________________________________________ > >> BaseX-Talk mailing list > >> BaseX-Talk at mailman.uni-konstanz.de > >> https://mailman.uni-konstanz.de/mailman/listinfo/basex-talk > >> > > _______________________________________________ > > BaseX-Talk mailing list > > BaseX-Talk at mailman.uni-konstanz.de > > https://mailman.uni-konstanz.de/mailman/listinfo/basex-talk > > > _______________________________________________ > BaseX-Talk mailing list > BaseX-Talk at mailman.uni-konstanz.de > https://mailman.uni-konstanz.de/mailman/listinfo/basex-talk > >
Quoted text · Jens Erat · 3 lines
> What about adding version information to db:system() and another > function db:version() to be able to retrieve version information in an > xquery-processable manner?
Good point; I think I'll add the version number to the INFO command output. As a result, it will also be retrievabe via db:system().
Thanks, C.
Quoted text · Jens Erat · 52 lines
> > -- > Jens Erat > > [phone]: tel:+49-151-56961126 > [mail]: mailto:email at jenserat.de > [jabber]: xmpp:jabber at jenserat.de > [web]: http://www.jenserat.de > > PGP: 350E D9B6 9ADC 2DED F5F2 8549 CBC2 613C D745 722B > OTR: AA2C 0B55 F8D5 CEED 8F4F 6EE1 1EBF DD62 5426 7899 > > Am 18.05.11 17:58, schrieb Christian Grün: >>> I'm trying to determine the BaseX version running a remote server. >> >> …true, that's not possible right now. Which solution would you prefer? >> >>> P.S. In the BaseX GUI the "Logs" tab shows me the logs of the local BaseX even when I connect to a remote BaseX - could be on puprpose, I just found it somewhat counter intuitive. >> >> …true; I've just changed the wording to "Local Logs". >> >> Christian >> >> >>> When I connect using the client on my local machine the server does not say which version it is >>> >>> When I use the GUI to connect to the remote server I can't find any info on the version. >>> >>> When I login to the remote machine and go to the server folder I can't find any info on which version it is. >>> >>> When I look at the logs in the .logs folder I can't find any info on the server version (I could not find the startup info that the server generates). >>> >>> I copied the BaseX.jar to a place where I could unpack it and found version "6.6" in the META-INF/maven/org.basex/basex/pom.xml file. >>> >>> Is there a more convenient way of determining the remote version that I missed? And did I actually find the correct version in the pom? >>> >>> Hartelijke groet, >>> >>> Huib Verweij. >>> >>> P.S. In the BaseX GUI the "Logs" tab shows me the logs of the local BaseX even when I connect to a remote BaseX - could be on puprpose, I just found it somewhat counter intuitive. >>> _______________________________________________ >>> BaseX-Talk mailing list >>> BaseX-Talk at mailman.uni-konstanz.de >>> https://mailman.uni-konstanz.de/mailman/listinfo/basex-talk >>> >> _______________________________________________ >> BaseX-Talk mailing list >> BaseX-Talk at mailman.uni-konstanz.de >> https://mailman.uni-konstanz.de/mailman/listinfo/basex-talk > >
Quoted text · Jan Vlčinský (CAD) · 2 lines
> I would expect version information as part of INFO command output. > Jan
..dito ;)
Quoted text · Christian Grün · 6 lines
>> What about adding version information to db:system() and another >> function db:version() to be able to retrieve version information in an >> xquery-processable manner? > > Good point; I think I'll add the version number to the INFO command > output. As a result, it will also be retrievabe via db:system().
Done; feel free to check out the latest snapshot.
Christian
Op 19 mei 2011, om 17:15 heeft Christian Grün het volgende geschreven:
What about adding version information to db:system() and another function db:version() to be able to retrieve version information in an xquery-processable manner?
Good point; I think I'll add the version number to the INFO command output. As a result, it will also be retrievabe via db:system().
Done; feel free to check out the latest snapshot.
Great, works for me.
However, checking out the latest using "git pull upstream master" gets me this repeatedly when building:
------------------------------------------------------------------------------- Test set: org.basex.test.query.simple.XQUPTest ------------------------------------------------------------------------------- Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.831 sec <<< FAILURE! test(org.basex.test.query.simple.XQUPTest) Time elapsed: 0.722 sec <<< FAILURE! java.lang.AssertionError: 1 wrong queries; [E] expected, [F] found: -- rep4: /up/cars/good/car/wheels[text()='5 fooboo'] [E] () [F] Possible bug? Your feedback is welcome: Contact: basex-talk at mailman.uni-konstanz.de<mailto:basex-talk at mailman.uni-konstanz.de> Version: BaseX 6.6.3 beta Java: Apple Inc., 1.6.0_24 OS: Mac OS X, x86_64 Stack Trace: java.lang.ArrayIndexOutOfBoundsException: 4 org.basex.util.Compress.pull(Compress.java:127) org.basex.util.Compress.unpack(Compress.java:106) org.basex.data.DiskData.txt(DiskData.java:211) org.basex.data.DiskData.text(DiskData.java:178) org.basex.index.DiskValues.get(DiskValues.java:202) org.basex.index.DiskValues.nrIDs(DiskValues.java:97) org.basex.data.Data.nrIDs(Data.java:190) org.basex.query.expr.CmpG.indexAccessible(CmpG.java:285) org.basex.query.path.AxisPath.index(AxisPath.java:164) org.basex.query.path.AxisPath.compPath(AxisPath.java:116) org.basex.query.path.Path.comp(Path.java:83) org.basex.query.QueryContext.compile(QueryContext.java:237) org.basex.query.QueryProcessor.compile(QueryProcessor.java:96) org.basex.core.cmd.AQuery.query(AQuery.java:75) org.basex.core.cmd.XQuery.run(XQuery.java:22) org.basex.core.Command.run(Command.java:314) org.basex.core.Command.exec(Command.java:296) org.basex.core.Command.execute(Command.java:71) org.basex.core.Command.execute(Command.java:83) org.basex.test.query.simple.QueryTest.test(QueryTest.java:82) sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) java.lang.reflect.Method.invoke(Method.java:597) org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44)
Hartelijke groet,
Huib Verweij.
Hi Huib,
sorry for the inconvenience. Due to a failing test case Maven refuses to build. I deactivated the corresponding module for now (speeding up XQUP replace statements). The latest repository state contains this fix.
Regards, Lukas
Quoted text · Huib Verwey · 95 lines
On Fri, May 20, 2011 at 11:47 AM, Huib Verwey <Huib.Verwey at mpi.nl> wrote: > > Op 19 mei 2011, om 17:15 heeft Christian Grün het volgende geschreven: > > What about adding version information to db:system() and another > > function db:version() to be able to retrieve version information in an > > xquery-processable manner? > > > Good point; I think I'll add the version number to the INFO command > > output. As a result, it will also be retrievabe via db:system(). > > > Done; feel free to check out the latest snapshot. > > > Great, works for me. > > However, checking out the latest using "git pull upstream master" gets me > this repeatedly when building: > > > ------------------------------------------------------------------------------- > Test set: org.basex.test.query.simple.XQUPTest > > ------------------------------------------------------------------------------- > Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.831 sec > <<< FAILURE! > test(org.basex.test.query.simple.XQUPTest) Time elapsed: 0.722 sec <<< > FAILURE! > java.lang.AssertionError: 1 wrong queries; [E] expected, [F] found: > -- rep4: /up/cars/good/car/wheels[text()='5 fooboo'] > [E] () > [F] Possible bug? Your feedback is welcome: > Contact: basex-talk at mailman.uni-konstanz.de > Version: BaseX 6.6.3 beta > Java: Apple Inc., 1.6.0_24 > OS: Mac OS X, x86_64 > Stack Trace: > java.lang.ArrayIndexOutOfBoundsException: 4 > org.basex.util.Compress.pull(Compress.java:127) > org.basex.util.Compress.unpack(Compress.java:106) > org.basex.data.DiskData.txt(DiskData.java:211) > org.basex.data.DiskData.text(DiskData.java:178) > org.basex.index.DiskValues.get(DiskValues.java:202) > org.basex.index.DiskValues.nrIDs(DiskValues.java:97) > org.basex.data.Data.nrIDs(Data.java:190) > org.basex.query.expr.CmpG.indexAccessible(CmpG.java:285) > org.basex.query.path.AxisPath.index(AxisPath.java:164) > org.basex.query.path.AxisPath.compPath(AxisPath.java:116) > org.basex.query.path.Path.comp(Path.java:83) > org.basex.query.QueryContext.compile(QueryContext.java:237) > org.basex.query.QueryProcessor.compile(QueryProcessor.java:96) > org.basex.core.cmd.AQuery.query(AQuery.java:75) > org.basex.core.cmd.XQuery.run(XQuery.java:22) > org.basex.core.Command.run(Command.java:314) > org.basex.core.Command.exec(Command.java:296) > org.basex.core.Command.execute(Command.java:71) > org.basex.core.Command.execute(Command.java:83) > org.basex.test.query.simple.QueryTest.test(QueryTest.java:82) > sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > java.lang.reflect.Method.invoke(Method.java:597) > > org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44) > > > Hartelijke groet, > > Huib Verweij. > > -- > Drs. Huib Verweij > Senior software developer - The Language Archive > Max Planck Institute for Psycholinguistics > P.O. Box 310 > 6500 AH Nijmegen > The Netherlands > t +31-24-3521911 > e huib.verwey at mpi.nl > w http://www.mpi.nl/ > > > _______________________________________________ > BaseX-Talk mailing list > BaseX-Talk at mailman.uni-konstanz.de > https://mailman.uni-konstanz.de/mailman/listinfo/basex-talk > >
Hi Lucas,
Op 20 mei 2011, om 12:32 heeft Lukas Kircher het volgende geschreven:
The latest repository state contains this fix.
it works and the INFO command reports the version number, great!
Hartelijke groet,
Huib Verweij.
Written for BaseX 6.6. BaseX may have changed since: please check the current documentation.