Re: [basex-talk] Maven repo 9.0
Hi Marc, true, because basex-xqj is not actually a project by BaseX, but by Charles Foster. Actually it can be found in its own Maven repository at http://xqj.net/maven/, although it seems the version sin the BaseX Maven repo are more up to date. Actually I don't really know who maintains these versions (I assume that Christian is updating these with major new versions). But because it is not a BaseX product nor domain I think it is not a good idea if we would sync it to Maven Central (under the artefact net.xqj.basex-xqj) ourself. So I see the following solutions: 1) We keep it as-is and when you want to use BaseX XQJ you have to add the BaseX Maven repo 2) The newly created basex-xqj are uploaded to the xqj Maven repo and when wanting to use it you have to add the repo 3) xqj also uploads to Maven Central I think 2) or 3) would be cleaner/better, but it is not within the control of BaseX. Maybe Christian has an opinion or some thoughts on this when he is back. Cheers Dirk Senacor Technologies Aktiengesellschaft - Sitz: Eschborn - Amtsgericht Frankfurt am Main - Reg.-Nr.: HRB 105546 Vorstand: Matthias Tomann, Marcus Purzer - Aufsichtsratsvorsitzender: Daniel Gr?zinger -Urspr?ngliche Nachricht- Von: Marc van Grootel [mailto:marc.van.groo...@gmail.com] Gesendet: Dienstag, 27. M?rz 2018 21:38 An: Kirsten, Dirk Cc: BaseX Betreff: Re: [basex-talk] Maven repo 9.0 Hi Dirk, Yes, it is synced to Maven Central now. The net.xqj:basex-xqj:9.0 dependency still requires adding the http://files.basex.org/maven repo though as it cannot be found on MC. Thanks, --Marc On Tue, Mar 27, 2018 at 5:12 PM, Kirsten, Dirk wrote: > Hi Marc, hi list, > > unfortunately something went wrong during Christians deploy process > and he is now on (a well-deserved) holiday. However, he wrote me about > it (as I setup the Maven Central deploy process and I think I just > "fixed" it (not really a fix, but using the UI...). It is release to > OSSHR and should be synced to Maven Central > (https://mvnrepository.com/artifact/org.basex) in a short while. > Note, that it is not release to the own BaseX Maven Repository - I am > not sure whether Christian did this on purpose (because havin the > files in Maven Central should be enough for anyone I guess) or just missed it. > > Cheers > Dirk > > > Senacor Technologies Aktiengesellschaft - Sitz: Eschborn - Amtsgericht > Frankfurt am Main - Reg.-Nr.: HRB 105546 > Vorstand: Matthias Tomann, Marcus Purzer - Aufsichtsratsvorsitzender: > Daniel Gr?zinger > > -Urspr?ngliche Nachricht- > Von: basex-talk-boun...@mailman.uni-konstanz.de > [mailto:basex-talk-boun...@mailman.uni-konstanz.de] Im Auftrag von > Marc van Grootel > Gesendet: Dienstag, 27. M?rz 2018 15:49 > An: BaseX > Betreff: [basex-talk] Maven repo 9.0 > > > Hi, > > First of all congrats with the release of the Spring edition. Nice > steady pace of quality updates. > > I wanted to test 9.0 by getting it via de Maven coordinates but > noticed that > 9.0 wasn't available from the basex Maven repo. Only 9.0-SNAPSHOT and > 9.0.1-SNAPSHOT. > > Is it possible to also make 9.0 available from org.basex:basex-api:9.0 > Maven coordinates? > > --Marc -- --Marc
Re: [basex-talk] Maven repo 9.0
Hi Dirk, Yes, it is synced to Maven Central now. The net.xqj:basex-xqj:9.0 dependency still requires adding the http://files.basex.org/maven repo though as it cannot be found on MC. Thanks, --Marc On Tue, Mar 27, 2018 at 5:12 PM, Kirsten, Dirk wrote: > Hi Marc, hi list, > > unfortunately something went wrong during Christians deploy process and he > is now on (a well-deserved) holiday. However, he wrote me about it (as I > setup the Maven Central deploy process and I think I just "fixed" it (not > really a fix, but using the UI...). It is release to OSSHR and should be > synced to Maven Central (https://mvnrepository.com/artifact/org.basex) in a > short while. > Note, that it is not release to the own BaseX Maven Repository - I am not > sure whether Christian did this on purpose (because havin the files in Maven > Central should be enough for anyone I guess) or just missed it. > > Cheers > Dirk > > > Senacor Technologies Aktiengesellschaft - Sitz: Eschborn - Amtsgericht > Frankfurt am Main - Reg.-Nr.: HRB 105546 > Vorstand: Matthias Tomann, Marcus Purzer - Aufsichtsratsvorsitzender: Daniel > Grözinger > > -Ursprüngliche Nachricht- > Von: basex-talk-boun...@mailman.uni-konstanz.de > [mailto:basex-talk-boun...@mailman.uni-konstanz.de] Im Auftrag von Marc van > Grootel > Gesendet: Dienstag, 27. März 2018 15:49 > An: BaseX > Betreff: [basex-talk] Maven repo 9.0 > > > Hi, > > First of all congrats with the release of the Spring edition. Nice steady > pace of quality updates. > > I wanted to test 9.0 by getting it via de Maven coordinates but noticed that > 9.0 wasn't available from the basex Maven repo. Only 9.0-SNAPSHOT and > 9.0.1-SNAPSHOT. > > Is it possible to also make 9.0 available from org.basex:basex-api:9.0 Maven > coordinates? > > --Marc -- --Marc
[basex-talk] child node problem
Hi All,
Thanks for this new release, which looks great!
I have found a problem though (see error message below), when running a query
like:
for $ee in collection("my-path-to-files")
where $ee//case[./aspect-values[@sign = "yes"]]
return
$ee
This works in version 8.6.7. The problem seems to be [./aspect-values[@sign =
"yes"]]: if I change it in [//aspect-values[@sign = "yes"]] it works fine also
in 9.0. Any idea? Thanks.
Best,
Giuseppe
ERROR MESSAGE
Error:
Improper use? Potential bug? Your feedback is welcome:
Contact: basex-talk@mailman.uni-konstanz.de
Version: BaseX 9.0
Java: Oracle Corporation, 1.8.0_151
OS: Mac OS X, x86_64
Stack Trace:
java.lang.ClassCastException: org.basex.query.value.item.Dummy cannot be cast
to org.basex.query.value.node.DBNode
at org.basex.query.expr.path.InvDocTest.get(InvDocTest.java:56)
at org.basex.query.expr.path.Path.index(Path.java:692)
at org.basex.query.expr.path.Path.optimize(Path.java:174)
at org.basex.query.expr.path.Path.optimize(Path.java:180)
at org.basex.query.expr.path.Path.compile(Path.java:157)
at org.basex.query.expr.gflwor.Where.compile(Where.java:53)
at org.basex.query.expr.gflwor.Where.compile(Where.java:1)
at org.basex.query.expr.gflwor.GFLWOR.compile(GFLWOR.java:101)
at org.basex.query.scope.MainModule.comp(MainModule.java:83)
at org.basex.query.QueryCompiler.compile(QueryCompiler.java:114)
at org.basex.query.QueryCompiler.compile(QueryCompiler.java:105)
at org.basex.query.QueryContext.compile(QueryContext.java:299)
at org.basex.query.QueryProcessor.compile(QueryProcessor.java:79)
at org.basex.core.cmd.AQuery.query(AQuery.java:78)
at org.basex.core.cmd.XQuery.run(XQuery.java:22)
at org.basex.core.Command.run(Command.java:257)
at org.basex.core.Command.execute(Command.java:93)
at org.basex.gui.GUI.exec(GUI.java:427)
at org.basex.gui.GUI.lambda$4(GUI.java:370)
at java.lang.Thread.run(Thread.java:748)
Compiling:
- pre-evaluate fn:collection([uri]) to document-node() sequence:
collection("/Users/mycomputer/Documents/... -> (db:open-pre("documents", 0),
...)
- rewrite cached path to = operator: *:aspect-values ->
(*:aspect-values/@*:sign = "yes")
- rewrite cached path to = operator: *:aspect-values ->
(*:aspect-values/@*:sign = "yes")
- rewrite descendant-or-self step(s)
- apply attribute index for "yes"
Optimized Query:
for $ee_0 in (db:open-pre("documents", 0), ...) where
$ee_0/descendant-or-self::node()/descendant::*:case[(*:aspect-values/@*:sign =
"yes")] return $ee_0
Query:
for $ee in
collection("/Users/mycomputer/Documents/act/03_p-valuesAfterReductionToPerfImp/documents")
where $ee//case[./aspect-values[@sign = "yes"]] return $ee
Universität Leipzig
Institute of Computer Science, Digital Humanities
Augustusplatz 10
04109 Leipzig
Deutschland
E-mail: cel...@informatik.uni-leipzig.de
E-mail: giuseppegacel...@gmail.com
Web site 1: http://www.dh.uni-leipzig.de/wo/team/
Web site 2: https://sites.google.com/site/giuseppegacelano/
Re: [basex-talk] Maven repo 9.0
Hi Marc, hi list, unfortunately something went wrong during Christians deploy process and he is now on (a well-deserved) holiday. However, he wrote me about it (as I setup the Maven Central deploy process and I think I just "fixed" it (not really a fix, but using the UI...). It is release to OSSHR and should be synced to Maven Central (https://mvnrepository.com/artifact/org.basex) in a short while. Note, that it is not release to the own BaseX Maven Repository - I am not sure whether Christian did this on purpose (because havin the files in Maven Central should be enough for anyone I guess) or just missed it. Cheers Dirk Senacor Technologies Aktiengesellschaft - Sitz: Eschborn - Amtsgericht Frankfurt am Main - Reg.-Nr.: HRB 105546 Vorstand: Matthias Tomann, Marcus Purzer - Aufsichtsratsvorsitzender: Daniel Gr?zinger -Urspr?ngliche Nachricht- Von: basex-talk-boun...@mailman.uni-konstanz.de [mailto:basex-talk-boun...@mailman.uni-konstanz.de] Im Auftrag von Marc van Grootel Gesendet: Dienstag, 27. M?rz 2018 15:49 An: BaseX Betreff: [basex-talk] Maven repo 9.0 Hi, First of all congrats with the release of the Spring edition. Nice steady pace of quality updates. I wanted to test 9.0 by getting it via de Maven coordinates but noticed that 9.0 wasn't available from the basex Maven repo. Only 9.0-SNAPSHOT and 9.0.1-SNAPSHOT. Is it possible to also make 9.0 available from org.basex:basex-api:9.0 Maven coordinates? --Marc
[basex-talk] Maven repo 9.0
Hi, First of all congrats with the release of the Spring edition. Nice steady pace of quality updates. I wanted to test 9.0 by getting it via de Maven coordinates but noticed that 9.0 wasn't available from the basex Maven repo. Only 9.0-SNAPSHOT and 9.0.1-SNAPSHOT. Is it possible to also make 9.0 available from org.basex:basex-api:9.0 Maven coordinates? --Marc
