[gdal-dev] Advice on deploying components that use GDAL

[Barry DeZonia]

Hey all,

I hope this is the right place for this email. I am a developer that has
written a java component that interfaces with the java bindings and allows
my app users to access gdal data.

The problem I have is that gdal seems to release somewhat often. I wrote my
code initially for 3.7 but later used 3.8 (and abandoned 3.7) due to some
new features present in the java bindings. Since then there have been gdal
releases for 3.9 and 3.10.

How should I release my (java jar) component?  One release version per gdal
release? Then am I forcing a similar fork in all downstream projects that
use my components? It seems so.

Now also imagine my component relies on something else that also has
multiple versions. I could get a combinatorial explosion in the number of
versions of my plugin.

And I also seem to need to make a decision on how to nicely target older
gdals that don't have the new java niceties of 3.8. Many people are using
gdal versions older than 3.8.

This whole topic is making my head spin a little. Any advice?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/gdal-dev/attachments/20241107/58828e3f/attachment.htm>