I don't think it's necessary to have a Maven-based build to publish to Maven, though it might be desirable...?
Xalan-J 's build is really not all that complex, as I recall. Haven't looked at the details recently, but isn't it mostly "compile all the code, generate docs, build jar"? -- /_ 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: Mukul Gandhi <muk...@apache.org> Sent: Wednesday, April 12, 2023 11:59:07 AM To: dev@xalan.apache.org <dev@xalan.apache.org> Subject: Re: XalanJ new git branches Hi Elliotte, Thanks for the thoughts. On Wed, Apr 12, 2023 at 8:30 PM Elliotte Rusty Harold <elh...@ibiblio.org> wrote: > 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. I think, XalanJ implementation and tests repos individually have significant codebase size and complexity. And these two different repos, are already functionally working fine, and integration between these two repos is also working fine and well defined, as also described within XalanJ readme file. Your suggestion, is to refactor the whole of XalanJ codebase (i.e, implementation and tests). I think, this issue is not a blocker issue, to proceed with further XalanJ development. > > 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. One issue, that's constantly coming up within these discussions, is publishing on Maven central. This is certainly, much beneficial for XalanJ users. But again, this (i.e, developing a XalanJ Maven build functionally equivalent to the current Ant build) shall require significant effort and time. Moreover, we already have a working XalanJ Ant build configuration ready which is working fine, that shall allow us to do further XalanJ development. Before a new XalanJ release, we can spend time to configure a Maven build for XalanJ. But until that is done, we can proceed with further XalanJ development with the current XalanJ Ant build. -- Regards, Mukul Gandhi --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org For additional commands, e-mail: dev-h...@xalan.apache.org
