There was discussion a few years ago about "master" having unfortunate connotations for some folks that "main" didn't, and a recommendation to switch over.
If that effort died, I'm a trifle disappointed but will let it lie where it fell. If it remains an open issue, though, I'd like to see us help lead in that direction. -- /_ Joe Kesselman (he/him/his) -/ _) My Alexa skill for New Music/New Sounds fans: / https://www.amazon.com/dp/B09WJ3H657/ Caveat: Opinionated old geezer with overcompensated writer's block. May be redundant, verbose, prolix, sesquipedalian, didactic, officious, or redundant. ________________________________ From: Gary Gregory <garydgreg...@gmail.com> Sent: Thursday, December 21, 2023 11:11:27 AM To: dev@xalan.apache.org <dev@xalan.apache.org> Subject: Re: Maven build on dev repos branch xalan-java-mvn-refactored >Reminder: At some point we should rename master to main, to conform to current >Git practice. Uh? Not according to git itself: "The default branch name in Git is master. As you start making commits, you’re given a master branch that points to the last commit you made." https://git-scm.com/book/en/v2/Git-Branching-Branches-in-a-Nutshell#:~:text=The%20default%20branch%20name%20in,branch%20pointer%20moves%20forward%20automatically.&text=The%20%E2%80%9Cmaster%E2%80%9D%20branch%20in%20Git%20is%20not%20a%20special%20branch. On Thu, Dec 21, 2023, 10:33 AM Joseph Kesselman <kesh...@alum.mit.edu<mailto:kesh...@alum.mit.edu>> wrote: I've been doing some work on xalan-test; there are a few small differences in where things land after the Maven build that it wants to be adjusted for... but I got sidetracked onto trying to finally get rid of the bootclasspath/endorsed kluges in favor of proper JAXP settings. I should separate those, get the essential merged so the maven build reports success, and then it's probably time to (finally!) consider cutting over to mvn. Mukul: Have you tested rebasing your work onto the Maven build? Or should we cut over and let you catch up? Reminder: At some point we should rename master to main, to conform to current Git practice. -- /_ Joe Kesselman (he/him/his) -/ _) My Alexa skill for New Music/New Sounds fans: / https://www.amazon.com/dp/B09WJ3H657/ Caveat: Opinionated old geezer with overcompensated writer's block. May be redundant, verbose, prolix, sesquipedalian, didactic, officious, or redundant. ________________________________ From: Gary Gregory <garydgreg...@gmail.com<mailto:garydgreg...@gmail.com>> Sent: Thursday, December 21, 2023 9:43:34 AM To: dev@xalan.apache.org<mailto:dev@xalan.apache.org> <dev@xalan.apache.org<mailto:dev@xalan.apache.org>> Subject: Re: Maven build on dev repos branch xalan-java-mvn-refactored That all sounds good to me. I imagine we would merge to master whatever it is we want to release. Gary On Thu, Dec 21, 2023, 9:09 AM Mukul Gandhi <muk...@apache.org<mailto:muk...@apache.org>> wrote: Hi Joseph & all, I've just got chance to run Maven build on XalanJ dev repos branch xalan-java-mvn-refactored. The Maven build ran successfully, and following XalanJ build artifacts were produced as well (within folder xalan-java-mvn-refactored\build), xalan-project-2.7.3-bin.zip, xalan-project-2.7.3-bin.tar.gz, xalan-project-2.7.3-src.zip, xalan-project-2.7.3-src.tar.gz This looks nice to me. I'm not sure. But maybe, can we try making a XalanJ 2.7.4 (is this XalanJ version number for the next release ok?) maven release from the dev repos branch xalan-java-mvn-refactored? -- Regards, Mukul Gandhi --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org<mailto:dev-unsubscr...@xalan.apache.org> For additional commands, e-mail: dev-h...@xalan.apache.org<mailto:dev-h...@xalan.apache.org>
