+1
At least in our environment it is impossible to create new layers with GS 2.7.x
with the included jdbc driver (ojdbc14.jar). However, creating new Oracle
stores succeeds which makes an user to believe that the fault is somewhere
else than in the driver. Better to drop the driver and advice
Hi all,
here is the pull request:
https://github.com/geoserver/geoserver/pull/1072
Since we are starting to receive bug reports caused by the old driver not
being
fully compatible with the Oracle store anymore, I'd be happy if we could
merge
this pull request before tomorrow's 2.7.1 release (no co
Hi,
There should also be a Accept license box. BTW. what do you like about this
part of the license:
"You may not:
- disclose results of any program benchmark tests without our prior consent."
I have liked how easy it is to install the Oracle plugin simply by unzipping
but still
+1 to drop.
The Oracle license states that it is not permitted to redistribute the
ojdbc jar by itself, but explicitly permitted to redistribute bundled
with software that uses it (and the GeoServer oracle plugin would seem
to meet this criterion).
However, we cannot comply with the export control provisio
Hi,
I'm writing to suggest we drop the old jdbc jar we are shipping with the
Oracle plugin.
Theoretically, we should not do it anyways, it's just that back then we got
a verbal confirmation
from an Oracle employee that is was fine to add it in our plugin.
But the driver is now very old, so unless
