hi,
so let’s make decisions here.
Seeing the discussion at http://logs.qgis.org/geonetwork/%23geonetwork.2010-10-12.log, the situation with Postgres drivers seems to be that we use either the one compatible with JDK1.5, which is not compatible with JDK1.6, or the other way around.
, the Postgres JDBC page says “If you are using the 1.6 JVM, then you should use the JDBC4 version”. It does not say that it is really not possible to use the JDBC3 driver with JDK1.6. Does anyone know about this for sure ?
Assuming things are really not backward- and forward-compatible, the questions we need to answer are :
-
what do we put in the default downloadable installer ? or,
-
do we provide 2 default downloadable installers ?
-
what does the buildscript do by default
My vote: I believe most production sites using GeoNetwork are running on JDK1.5, as they are often governmental institutes etc. that are often not at the bleeding edge of new technologies.
So, default support for JDK1.5 in the downloadable installer and in the buildscript. No 2 versions of downloadable installers, that could be the beginning of a drama.
What do you all think, and can we decide on this ? It is bothersome to developers too to have to adjust things everytime after a clean checkout and build.
Kind regards
Heikki Doeleman
On Fri, Oct 8, 2010 at 9:49 PM, jose garcia <josegar74@anonymised.com> wrote:
Hi Heikki
I think I commented this is a previous IRC meeting, but someone commented that also Java 1.5 is no longer supported by Oracle and the release of 2.6.0 was quite near so no much priority on this in that moment.
The new driver for Postgres supports JDBC4 (also same for MySql driver provided), but not sure if is really required this support in any functionality. If someone can confirm this should be good, otherwise I think we can downgrade to JDBC3 drivers supporting both Java 1.5 and 1.6.
Regards,
Jose Garcia
On Fri, Oct 8, 2010 at 4:01 PM, heikki <tropicano@anonymised.com.31…> wrote:
hello list,
In GeoNetwork 2.6.0, the Postgres JDBC driver was upgraded. This new driver version is compiled with JDK1.6, making it impossible to run GeoNetwork 2.6.0 on JDK1.5 if you use Postgres.
Was this upgrade absolutely necessary, or was there some compelling reason for it ?
If not I propose that we downgrade back to our earlier version, so as not to break compatibility for JDK1.5 environments.
If there is a very good reason for this upgrade, then I’d say we should officially stop supporting JDK1.5 environments in all configurations – it is confusing to need to state that we support it when using some DBMSs, and not when using other ones.
What do you think ?
Kind regards
Heikki Doeleman
Beautiful is writing same markup. Internet Explorer 9 supports
standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3.
Spend less time writing and rewriting code and more time creating great
experiences on the web. Be a part of the beta today.
http://p.sf.net/sfu/beautyoftheweb
GeoNetwork-devel mailing list
GeoNetwork-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geonetwork-devel
GeoNetwork OpenSource is maintained at http://sourceforge.net/projects/geonetwork