Opened 9 years ago

Closed 5 years ago

#222 closed defect (wontfix)

Making GDAL Java bindings work

Reported by: Marvin Owned by: moovida
Priority: major Component: Package
Version: Keywords: Java GDAL UnsatisfiedLinkError compatibility
Cc: moovida, warmerdam

Description

Hey, this is about the OSGeo4W GDAL and GDAL Java package. It does not seem to work properly due to some compatibility issues between GDAL libraries, leading to errors according to someone in this thread:

http://osgeo-org.1803224.n2.nabble.com/Using-the-GDAL-OGR-Java-bindings-with-the-OSGeo4W-environment-td6301272.html#a6301448

The problem occurs, e.g. if you try to run ogr.Open(), leading to an UnsatisfiedLinkError?

Could someone solve this? Thanks.

Change History (5)

comment:1 Changed 9 years ago by moovida

Hmm, the reason we have an older gdal binding in the java package, is because uDig and geoserver (at least these are the ones I know of) bindings require those older bindings and would not work with an updated version.

right now the only solution is to upload a customized java virtual machine to be used with the project that needs it.

We are in the process to start to migrate to the new binding versions of gdal-java, but I can't say right now when that will be.

comment:2 Changed 9 years ago by moovida

Cc: moovida added

comment:3 Changed 8 years ago by warmerdam

Cc: warmerdam added
Owner: changed from osgeo4w-dev@… to moovida

The inclusion of old GDAL stuff in the java package is causing problems - for instance the gdalinfo.exe sometimes supercedes the primary gdalinfo. This isn't appropriate.

If GDAL 1.7 bindings are necessary they should live in a version specific place and should be packaged separately from the Java base package. Likewise for other surprising stuff in this package like ECW libraries.

comment:4 Changed 5 years ago by moovida

Just as a side note, I am going to remove java as a library package. Since no one came back on taking over its maintenance (which puzzles me a bit), for now I think it is ok to remove it. If something comes up, it will most probably be best to install java as an application, and reference it from any other project, if necessary.

comment:5 Changed 5 years ago by jef

Resolution: wontfix
Status: newclosed

java and reverse dependencies have marked _obsolete (unmaintained, orphaned)

Note: See TracTickets for help on using tickets.