When it comes down to it, it’s also possible to manually upload a release to the staging Nexus repository. It’s just like 10x more annoying than using a build plugin. Thankfully, there are numerous ASF projects using Gradle, so there are plenty of examples.
I have some SBT samples, too, if you need them. On Fri, Aug 9, 2019 at 04:24, Chetan Mehrotra <chetan.mehro...@gmail.com> wrote: > Hi Team, > > To allow end users make use of Standalone OpenWhisk we should perform > a release of OpenWhisk core repo. > > I believe following aspects need to be considered for any such release > > 1. Any reference to "nightly" tag should be replaced with actual > specific tag (not even latest). This should be done in runtimes.json > and standalone conf file. Here we would need to check if any > downstream runtime/project need to be released. For example we would > need to release the apigateway for Api gateway support in standalone > to work > > 2. (optional) Publish OpenWhisk related jars to Maven. This would > involve pushing the jars to a staging Nexus repo [1], [2] and then > releasing post passage of vote. This process is standardinzed for > Maven based project. So would need to find out how its done for Gradle > based projects > > > Doing #2 would need some more work so for now we can just aim for #1. > > Any thoughts on what else needs to be taken care of for such a > release. One possible approach can be > > 1. Create anew branch > 2. Make required changes to freeze coordinates of dependencies > 3. Perform release and tag > 4. Delete the branch post vote passed > > Chetan Mehrotra > [1] http://www.apache.org/dev/publishing-maven-artifacts.html > [2] > https://sling.apache.org/documentation/development/release-management.html#staging-the-release-candidates > -- Matt Sicker <boa...@gmail.com>
