google
Explicitly state GFJ version to use for Eclipse plugin build
Re-adds the GJF version specification to the Eclipse plugin pom.
This decouples the GJF version from the Eclipse plugin version. As a result, it is possible to increase the Eclipse plugin version without changing the used GJF core version (e.g. in cases where you want to increase the patch level of the plugin version when deploying fixes for the Eclipse plugin).
Additionally, it allows for easier builds with local snapshot versions of GJF.
Also updates the README to link to the current release. Removes explicit mention of the Eclipse plugin release 1.6. Links to the release page instead of a specific JAR file so that the link does not have to be updated with every release.
I think it should be possible to do snapshot builds of the plugin even without this change?
Yes, it is possible without the change. Maybe my commit message was misleading. I am not the biggest fan of using a single version argument defining both the version of the Eclipse plugin and the version of the used GFJ jar. This approach means that you always have to change the version of the Eclipse Plugin if you want to change the GJF version, e.g. for testing. But this is more a matter of taste.
The more important use case for separate version arguments is the possibility of independent releases for the Eclipse plugin (e.g. bugfix releases). The way I understand it, it is not possible to only increase the Eclipse plugin version with the current handling. If we were to set the plugin version to 1.11.1 to release an updated version of the plugin without switching GJF versions, the build would look for a GJF jar with the same version (which it would not be able to find).
The more important use case for separate version arguments is the possibility of independent releases for the Eclipse plugin (e.g. bugfix releases)
Thanks, that makes sense.
The main disadvantage from my perspective is that it's another version number I have to remember to update when doing releases, and the more streamlined the release process is the easier it is to do more often :)
Does it seem workable to you to change to something like the approach in this PR if/when we need to do a patch release of the Eclipse plugin, but leave it using the same version numbers for now so there's only one version number to update?
