Ghidra: Allow Multiple Extension Versions

[astrelsky]

Is your feature request related to a problem? Please describe.
Currently only one ghidra version may be specified in an extension.properties version field. This requires either an extension distributor to release multiple different releases of an identical extension with the only difference being the version field or requiring the end user to change the value to their version of ghidra.

Describe the solution you'd like
Allow either a range of ghidra version to be specified or to specify a comma separated list of versions.

Describe alternatives you've considered
See the Building section of this repository's README.

[lab313ru]

I think it's impossible because of base classes changing. Some methods are changing its signatures, some ideas become unused. So, how would you plan to support such things?

[astrelsky]

I think it's impossible because of base classes changing. Some methods are changing its signatures, some ideas become unused. So, how would you plan to support such things?

If the extension/plugin maker knows their plugin wouldn't be compatible with older/newer versions they would omit the incompatible version. If nothing changed between versions which affects the plugin why should it need to be redistributed with the only change being a version number.

I am literally using the same compiled jar of my plugin for 3 different builds of ghidra with the only change being the version number in the extension.properties.

[ryanmkurtz]

This is a big limitation with our extension system. What you are suggesting doesn't address the real problem, but it would be simple to implement and make it slightly less annoying to distribute. It would be up to extension writer to thoroughly test their extension with new versions of Ghidra before bumping the supported range up.