You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I do have a Java project with some resource XML files which should be validated against each other with XQuery using BaseX. It set everything up like shown in https://docs.basex.org/main/Integrating_IntelliJ_IDEA whereas selecting "Standalone Instance" when configuring the Query Processor Instance.
Running XQuery scripts from terminal with BaseX works just fine but using a IntelliJ Run Configuration unfortunately does not work as expected because somehow user.dir is set to C:\Program Files\JetBrains\IntelliJ IDEA 2024.2.1\bin and not to the executing directory. This is clearly observable by running the simple query
proc:property('user.dir')
via run configuration.
Is this a known issue? And could user.dir be overwritten somehow as currently passing options is not available? Or is it possible to query the current $PROJECT_ROOT set by IntelliJ to build a valid absolute path?
The text was updated successfully, but these errors were encountered:
Hi,
I do have a Java project with some resource XML files which should be validated against each other with XQuery using BaseX. It set everything up like shown in https://docs.basex.org/main/Integrating_IntelliJ_IDEA whereas selecting "Standalone Instance" when configuring the Query Processor Instance.
Running XQuery scripts from terminal with BaseX works just fine but using a IntelliJ Run Configuration unfortunately does not work as expected because somehow
user.dir
is set toC:\Program Files\JetBrains\IntelliJ IDEA 2024.2.1\bin
and not to the executing directory. This is clearly observable by running the simple queryvia run configuration.
Is this a known issue? And could
user.dir
be overwritten somehow as currently passing options is not available? Or is it possible to query the current$PROJECT_ROOT
set by IntelliJ to build a valid absolute path?The text was updated successfully, but these errors were encountered: