+1 for moving test into xalan-j. Having test be a separate project goes back to earlier days of XSLT development, when one of our goals was to help drive XSLT acceptance and standardization, and the tests were intended to be available for use with and validation of other processors, not just Xalan. One outcome of that, of course, is that they're all functional tests; unit tests would be non-portable.
There's no reason we couldn't continue to support that usage if we moved them into Xalan, of course. Folks would have to download more to build the test suite, but given that network speeds and storage are both orders of magnitude better than when we started that shouldn't be a serious hardship. (I just installed a 30GB package on one of my own machines...) This might require that we rework the build scripts a bit. But we already have some confusion over whether xalan-test gets unpacked as a peer of xalan-java or a child of it, and making it clearly contained would reconcile that. +0.75 for github-first. Putting the "source of truth" copy at the place where the most people will look for it makes sense to me; I just haven't thought it all the way through to consider whether this means discontinuing the other locations entirely or merely inverting the relationship. -- /_ Joe Kesselman (he/him/his) -/ _) My Alexa skill for New Music/New Sounds fans: / https://www.amazon.com/dp/B09WJ3H657/ () Plaintext Ribbon Campaign /\ Stamp out HTML mail! ________________________________ From: Elliotte Rusty Harold <elh...@ibiblio.org> Sent: Wednesday, April 12, 2023 10:59:23 AM To: dev@xalan.apache.org <dev@xalan.apache.org> Subject: Re: XalanJ new git branches On Wed, Apr 12, 2023 at 2:53 PM Mukul Gandhi <muk...@apache.org> wrote: > > Hi Joseph, > Thanks for the thoughts, and I agree with you. > > On Wed, Apr 12, 2023 at 7:45 PM Joseph Kesselman <kesh...@alum.mit.edu> wrote: > > > > Why would you fork a new development branch from anything but master/main? > > We shall first, make xalan-java repos's master branch's contents same > as that of the branch xalan-j_2_7_1_maint. +1 > Then we'll create the > branch xalan-j_xslt3.0 from this newly updated master branch. > +0 > For xalan-test repos, we can directly create branch > xalan-j_xslt3.0_tests from the master branch. -1 We should combine the test and the model repos. Two repos is very inconvenient. The goal is a single repo where single commands like "ant install" (or whatever it's called) compile everything, run all tests, and package the results up. Also, we should move to Github first development. Most other Apache projects already do this. That Xalan doesn't is simply due to its age (predating git) and lack of developers for the last decade. The lack of developers is exacerbated by idiosyncratic build processes and development tools. Spending time moving to de facto standard processes (tests in the same repo as the code, Github first, publishing on Maven Central) should easily pay back the effort expended. -- Elliotte Rusty Harold elh...@ibiblio.org --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org For additional commands, e-mail: dev-h...@xalan.apache.org
