The original problem went away in 1.12.1, but running a release from a pom in a subfolder like compiler-build-tools exposed a different bug. It is being tracked as https://issues.apache.org/jira/browse/SCM-932
I even supplied a test case this time. I am hopeful they will accept it. I understand it isn't ideal to use a snapshot version, and we'll certainly switch to their released version when it shows up. Maven's release plugin does not complain if the scm provider plugins have a snapshot version. That's how we got 0.9.6 out the door. -Alex On 4/8/20, 10:35 AM, "Christofer Dutz" <[email protected]> wrote: Hi Alex, well it seems that with JGit you were having a problem before and you sent the folks a patch to fix that which they never accepted as I think they were missing a testcase for it. So the version on the server was a manually patched one. I think this isn't ideal for releases same with having SNAPSHOT plugins in the build. Especially not regarding reproducibility (even if technically this shouldn't have an influence on the generated artifacts, I have to admit) Have you found a different solution? One that works without patching plugins? Chris Am 08.04.20, 19:03 schrieb "Alex Harui" <[email protected]>: I have been working on it. You can tell by the emails about the release steps. However, I've lost several days trying to fix a bug in Maven's JGit implementation. I didn't like the workaround of storing someone's login name and email on the CI server. I think I have a solution so hopefully will make better progress over the next several days. If someone thinks they can get through the first 40 steps sooner, they are welcome to do so, but it will probably slow me down as I will have to check their work. I'm growing very tired of the negative and incorrect FUD. It will not take us 13 weeks and to suggest so is not helpful. I'm sorry I did not understand that Maven's latest JGit had a bug before giving the estimate. The older version I had patched was working correctly for us for 0.9.6 but with the new Maven changes it exposed a new bug. If people want more insight into what I'm doing every evening, I will send a short email about it, but again, that also takes up my time. -Alex On 4/8/20, 3:39 AM, "Carlos Rovira" <[email protected]> wrote: Hi Yishay, we know Alex is working on it, we are saying to continue in parallel branches, since that doesn't help us in releasing 0.9.7 sooner. He was able to reach step 2 in one week. That's not one step per day as announced. In this progression will have 0.9.7 not before 13 weeks. Can we allow us this? El mié., 8 abr. 2020 a las 12:12, Yishay Weiss (<[email protected]>) escribió: > My impression was that Alex was working on integrating the latest Maven > changes in the CI release steps. I’ll take over as soon as he’s got that > polished. Alex, let me know if there’s anything I can do to speed things up. > > > From: Carlos Rovira<mailto:[email protected]> > Sent: Wednesday, April 8, 2020 12:05 PM > Subject: About Releasing 0.9.7 > > Hi all, > > I think people are waiting for us to release 0.9.7. We shouldn't postpone > it, since we have all we required. > It seems other doesn't have the cycles to do so. Can I take over? > > Then, other(s) can work in parallel to solve other convenient issues like > for example CI steps. > > Thanks! > > -- > Carlos Rovira > https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7Cb8f26ff9a66440f06e4608d7dbe32aba%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637219641036924392&sdata=WBjmXClujCtSQe6iWFC8Gs%2FOAOyPmH5t0Sy11TYEn8s%3D&reserved=0 > > -- Carlos Rovira https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7Cb8f26ff9a66440f06e4608d7dbe32aba%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637219641036924392&sdata=WBjmXClujCtSQe6iWFC8Gs%2FOAOyPmH5t0Sy11TYEn8s%3D&reserved=0
