And Nexus isn't an Apache thing AFAICT. You might have to read up on how it integrates with Maven.
Thanks for offering to help out on the Maven side. I'm concerned that you can't just take manually/locally built artifacts and follow the steps to publish those artifacts. I think those steps might be expecting a staging repository with artifacts produced from a branch it created in earlier steps. Regardless, we need to get more consensus around whether we will try process #3. -Alex On 6/16/17, 12:08 PM, "Josh Tynjala" <joshtynj...@gmail.com> wrote: >You're going to want to get your signing key ready: > >https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apach >e.org%2Fdev%2Frelease-signing.html&data=02%7C01%7C%7C473b0bd826324b2bdb730 >8d4b4eb24ab%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C63633236940145485 >9&sdata=NEAgBKcwNEQ3%2BAkmVD8Jg3cWL3So1TAYd2w45LSkvN4%3D&reserved=0 > >- Josh > >On Fri, Jun 16, 2017 at 11:40 AM, piotrz <piotrzarzyck...@gmail.com> >wrote: > >> Hi Alex, >> >> I think option 3 is almost what I think we should do. >> >> - Ant - examining should be same as it was by Approval script - No >>change >> here. >> >> - Maven: >> 1) Build Maven from sources downloaded by Approval script (I think it >> should >> be possible to build FlexJS and Falcon) or checkout release branch and >> build >> it. Typedefs should also be examined by that. >> 2) Perform Maven steps: - I think I can handle that. For this release we >> will be able to do only part of those steps. Let me explain why: >> >> Step 1-2) Should be done as a first thing - cause as part of that step >>we >> are creating new branch for the release - We already have it. >> ("release0.8.0) - As yo probably notice I did this steps and commit new >> branch, but that was a mistake and Josh helped me understand it. - I did >> revert. Almost manually changed develop to 0.9.0-SNAPSHOT >> >> Step 4) That's the mysterious for me a bit, cause as I understand after >> step >> 1-3 we have release branch where our version is 0.8.0-SNAPSHOT (That is >>our >> branch) and develop branch is in version 0.9.0-SNAPSHOT. - I did perform >> this step cause we were in exactly this situation. >> >> Maven asked me about "next development version" when I was performing >>this >> step - Which was unnecessary, cause I did setup my development version >>on >> "develop", so I was trying to set "0.8.0", but it didn't work. I >>decided to >> do this manually on our "release0.8.0" branch. >> >> Steps 5 - 8) This is what I should do next if you Alex and of course >>others >> also agreed that we can start VOTE. I'm only concerns about signing >> artifacts - not sure what is this mean, but I hope Maven will do this >>for >> me. >> >> As for the login to nexus - That is also what I need to figure out, but >>I'm >> assuming that as PMC I have access to Apache nexus.'' >> >> Waiting for thoughts and green light. >> >> Thanks, >> Piotr >> >> >> >> >> ----- >> Apache Flex PMC >> piotrzarzyck...@gmail.com >> -- >> View this message in context: http://apache-flex- >> development.2333347.n4.nabble.com/DISCUSS-Discuss-Release- >> Apache-FlexJS-0-8-0-RC1-tp62274p62431.html >> Sent from the Apache Flex Development mailing list archive at >>Nabble.com. >>
