Hi, Chris: This sounds like a great milestone achieved. Can I ask you to stay in the discussion for a few more days, in case someone runs into something that needs further clarification?
Thank you. a On Sun, Mar 21, 2021 at 9:54 AM Christofer Dutz <[email protected]> wrote: > Hi all, > > So, I am now considering my Job on the Maven part of the Royale build done. > > You should now: > > * Have a fully working Maven build including tooling for easy > onboarding > * Have a fully working Jenkins Setup on Apache Infra that should not > stop working regularly because of exceeded resource-credits ( > https://ci-builds.apache.org/job/Royale/) > * Have a fully working distribution built with Maven > * Have nightly distributions available on https://nightlies.apache.org > which could be used in the installer ( > https://nightlies.apache.org/Royale/Royale-asjs/) > * Have a working Maven release-build, which could be used to do > Maven-based releases (If you stick to typical Maven release requirements > and not the ones the project decided on ... I can't say which of these > might not be satisfied, but I would like you to challenge, if they are > really needed) > * Have a tutorial Video I did, explaining how to release Apache Royale > with Maven, here: > https://drive.google.com/drive/folders/1BDKG-zPW3CoWLI0KQJDO5PGyEJQtKRb4?usp=sharing > > I'm going to leave the discussion on what to do with this up to you. > > I consider my work on the Maven part of Royale done, which I strangely > still felt responsible for, even after being kicked out of the project some > years ago. > > You should now be able to continue on your own. > > Good luck, > Chris > -- Andrew Wetmore http://cottage14.blogspot.com/
