Hello I just commited some fixes. Hopefully all the files have the correct headers now. I also removed the gradle wrapper. Now you have to create the wrapper yourself when you first clone the project. Seems like the easiest way to avoid the binary issue. I think I've got the issues fixed so I can try and put RC2 together soon. Hopefully my key issue is fixed as well. Maybe someone could check for me.
Cheers, Ian On Tue, 2 Apr 2019, 15:10 Sagar, <kumarsagar15...@gmail.com> wrote: > @Ian Dunlop <ianwdun...@gmail.com> Are you working on the issues or do I > make the change? > > > > > > On Mon, Apr 1, 2019 at 9:41 PM Ian Dunlop <ianwdun...@gmail.com> wrote: > >> Hello, >> >> The key fingerprint is the same as listed in the KEYS file. Does that >> mean the key is the same? >> >> Cheers, >> >> Ian >> >> Sent from Mail for Windows 10 >> >> From: Stian Soiland-Reyes >> Sent: 01 April 2019 16:43 >> To: Ian Dunlop >> Cc: dev@taverna.incubator.apache.org >> Subject: RE: [DISCUSS] Release Apache Taverna Mobile 1.0-incubating-RC1 >> >> You'll also need to update the KEYS file in dist. >> >> On Mon, 1 Apr 2019 13:39:40 +0100, Ian Dunlop <ianwdun...@gmail.com> >> wrote: >> > Hello, >> > >> > @Sagar don’t forget to give it a +1 on the [VOTE] thread if you think >> it passes all the Apache release criteria. I think I just posted my VOTE to >> the DISCUSS thread – not sure message threading is working correctly in my >> email client. Apologies for any confusion. >> > >> > I’ve updated my key on the keyservers (gpg & ubuntu though they should >> both sync anyway). Let’s see if that fixes things because I’m sure I’ve >> updated them before. >> > I guess we should give them 24 hours to sort themselves out and then >> gpg --refresh-keys to update your local keys. >> >> > > -- > > Warmest regards > Sagar > Software Developer > Lattice Innovations Pvt. Ltd. >
