If gradle-release is tricky we can just do it manually and document in the releasing page what we had to do -- perhaps a shell script.
On 25 October 2017 at 18:29, Ian Dunlop <[email protected]> wrote: > Hello, > > @stain haven't used gradle-release but thought it looked like a good idea > @mark We had planned to just use the standard android packaging tools. If > there is a better way or a reason that we shouldn't then we are up for > anything. > > Cheers, > > Ian > > On 23 October 2017 at 14:46, Mark Fortner <[email protected]> wrote: > >> Just out of curiosity, I was wondering if you were using Java's packager >> for this? It has the ability to do native packaging, including desktop and >> mobile (both iOS android). >> >> Regards, >> >> Mark >> >> On 20 Oct 2017 8:55 a.m., "Stian Soiland-Reyes" <[email protected]> >> wrote: >> >> > Gradle-release sounds brilliant! Avoid pitfalls like snapshot >> dependencies >> > etc, as well as helping multiple people be release manager. >> > >> > Is it difficult to get it to work with android sdk..? >> > >> > >> > >> > On 19 Oct 2017 1:39 pm, "Ian Dunlop" <[email protected]> wrote: >> > >> > > Hello, >> > > >> > > When we release Taverna Mobile I imagine we will need to modify >> > > https://taverna.incubator.apache.org/community/releasing. Do we want >> to >> > > use >> > > a maven like release process for gradle >> > > https://github.com/researchgate/gradle-release ? Or do we just want to >> > > build, tag source code, upload .apk to staging repo? >> > > >> > > Cheers, >> > > >> > > Ian >> > > >> > >> -- Stian Soiland-Reyes http://orcid.org/0000-0001-9842-9718
