If you connect to DataBase with XDriverManager.getConnectionWithInfo():
JavaDriverClassPath put in Info is not added to the User ClassPath.
As a workaround you must add JDBC driver tar file in Tools - Options - LibreOffice - Advanced - Class Path... - Add Archive...
Steps to Reproduce:
1. Install gDriveOOo (or oneDriveOOo or DropboxOOo) with the required extensions (OAuth2OOo and CloudUcpOOo) from; https://github.com/prrvchr/gDriveOOo
2. Try to connect after installation: Don't work...
3. Add User ClassPath like: https://github.com/prrvchr/CloudUcpOOo/blob/master/README.md after restart work fine...
Need modification of User ClassPath like: https://github.com/prrvchr/CloudUcpOOo/blob/master/README.md after restart work fine...
No need modification of User Class Path (like in OpenOffice)
User Profile Reset: Yes
A new major release of LibreOffice is available since this bug was reported.
Could you please try to reproduce it with the latest version of LibreOffice
from https://www.libreoffice.org/download/libreoffice-fresh/ ?
I have set the bug's status to 'NEEDINFO'. Please change it back to
'UNCONFIRMED' if the bug is still present in the latest version.
I confirm that I can reproduce the bug with version 220.127.116.11 under Linux.
Apparently it doesn't happen on Windows.
I install LibreOffice under Ubuntu using the PPA:
in order to access the latest versions.
the workaround is to not install or uninstall the following packages:
It is possible to reproduce the malfunction by installing these two extensions:
Although the jar archive of Hsqldb 2.5.0 is present in the gContactOOo extension, it cannot be used if the integrated hsqldb driver is installed.
Do you have some information about the actual failure you experience (like the backtrace of a thrown java.lang.NoClassDefFoundError)?
As documented at offapi/com/sun/star/sdbc/JDBCConnectionProperties.idl and implemented at connectivity/source/drivers/jdbc/JConnection.cxx, JavaDriverClassPath is only used by the class loader that loads JavaDriverClass. It is not meant to end up on the global class path that can be modified via "Tools - Options... - LibreOffice - Advanced - Class Path..."
(By the way, <https://github.com/prrvchr/CloudUcpOOo/blob/master/README.md> as retrieved right now does not contain any information on "modification of User ClassPath" that you mention in comment 0.)
If you want to reproduce the problem just install the extension gContactOOo:
and during the first launch a test is made on the version of the Hsqldb driver loaded and if the version is correct the database is created... else an error occurs and displays the version of hsqldb.jar currently loaded.
I have two options to work around the problem:
Not install or uninstall the following packages:
Add hsqldb.jar to the global class path that can be modified via "Tools - Options... - LibreOffice - Advanced - Class Path...
I think the title is wrong, the JVM ClassPath is well modified but the jar archive is not placed at the beginning of the ClassPath...
(In reply to Stephan Bergmann from comment #3)
> JavaDriverClassPath is only used by the class loader that loads JavaDriverClass.
> It is not meant to end up on the global class path
I do not know what happening in Java, but what is certain is that it is impossible to use an archive already present on the system, because if exists it is loaded ...
And this is confirmed by the possibility of getting around the problem by not installing the basic drivers. (for me package is: libreoffice-sdbc-hsqldb and libhsqldb1.8.0-java)
it should also be noted that I did not manage to reproduce the problem under Windows where everything seems to work correctly (and the same under OpenOffice).
Could you please try to reproduce it with the latest version of LibreOffice from https://www.libreoffice.org/download/libreoffice-fresh/ ?
I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the bug is still present in the latest version.
This bug has been in NEEDINFO status with no change for at least
6 months. Please provide the requested information as soon as
possible and mark the bug as UNCONFIRMED. Due to regular bug
tracker maintenance, if the bug is still in NEEDINFO status with
no change in 30 days the QA team will close the bug as INSUFFICIENTDATA
due to lack of needed information.
For more information about our NEEDINFO policy please read the
wiki located here:
If you have already provided the requested information, please
mark the bug as UNCONFIRMED so that the QA team knows that the
bug is ready to be confirmed.
Thank you for helping us make LibreOffice even better for everyone!
Please read this message in its entirety before proceeding.
Your bug report is being closed as INSUFFICIENTDATA due to inactivity and
a lack of information which is needed in order to accurately
reproduce and confirm the problem. We encourage you to retest
your bug against the latest release. If the issue is still
present in the latest stable release, we need the following
information (please ignore any that you've already provided):
a) Provide details of your system including your operating
system and the latest version of LibreOffice that you have
confirmed the bug to be present
b) Provide easy to reproduce steps – the simpler the better
c) Provide any test case(s) which will help us confirm the problem
d) Provide screenshots of the problem if you think it might help
e) Read all comments and provide any requested information
Once all of this is done, please set the bug back to UNCONFIRMED
and we will attempt to reproduce the issue. Please do not:
a) respond via email
b) update the version field in the bug or any of the other details
on the top section of our bug tracker