pom-scijava icon indicating copy to clipboard operation
pom-scijava copied to clipboard

Published 20 hours ago • verified publisher icon scijava

Consider using the GitHub Release Maven Plugin

Open ctrueden opened this issue 11 years ago • 2 comments

The GitHub Release Maven Plugin integrates GitHub Releases with Maven deployment. We should consider leveraging this plugin to make it easy to release SciJava-based software via GitHub Releases.

ctrueden avatar Feb 17 '14 21:02 ctrueden

Another advantage of doing releases on GitHub is that it might enable us to switch to jitpack.io for deploying Maven artifacts.

ctrueden avatar Sep 25 '18 15:09 ctrueden

There's also https://github.com/RagedUnicorn/github-release-maven-plugin as an alternative Maven plugin, which might be better suited and has more recent commits.

See also some related discussion on the pyimagej gitter channel.

imagejan avatar Sep 22 '21 14:09 imagejan

After seeing Jitpack in action for years, I no longer want to use it. Using cryptographic hashes as versions is too confusing, since they are not sensibly ordered.

I'm also hesitant to embrace GitHub Releases in general, since I'm not sure what the advantages of using it would be. It ties us more tightly to GitHub (something I'm always resistant to do, in case we ever need to switch). We don't need the binary artifact hosting since we already have maven.scijava.org and oss.sonatype.org. It is a place where release notes could go, but we don't really do release notes yet (see this thread on forum.image.sc for related discussion), and maybe those should live in a file in the repository itself anyway?

Anyway, I have no plans to work on this, nor has anyone else stepped up, so I'm closing as not planned for now.

ctrueden avatar Mar 08 '23 00:03 ctrueden

Currently, the only benefit I see for creating a 'release' for every 'tag' on GitHub, is that the release versions could be automatically linked to a zenodo.org DOI. There's no need for the GitHub release to contain any binary files (besides the automatically added zipped source) or any release notes or other comments. A minimal, empty release would just allow to cite each component using a DOI, that's all. In addition (complementary to zenodo, or independent from it), we could adopt the citation file format and add a CITATION.cff file to each repository (in an automated way).

imagejan avatar Mar 08 '23 10:03 imagejan