Just a reminder: You do not need to be a committee to contribute to the Xalan 
project. As I've just demonstrated, you can work on a fork rather than a 
branch, then submit a pull request against that fork for the 
committers/approvers to evaluate.

So if Maven build is your top priority, _you_ can implement it and propose it. 
You can even invite folks to collaborate on it.

Or you can pay someone to do this.

Open source in action. If you need it now, make it happen. Otherwise you wait 
for someone else to be interested enough make it happen.


The Xalan _project_ is a big one, but it's build is relatively straightforward 
compared to some I've worked on. The biggest problem I see in moving to Mavin 
would be resolving jarfile dependencies; some of them won't be in Maven and the 
problem recurses.


As noted, making the project's Mavin _release_ cleaner is a separable question, 
and that's the one that seems to be the biggest ask here. It's probably worth 
making that its own issue and prioritizing it higher.  See earlier comments 
about how to actually make it happen.


For what it's worth,  I can probably be bribed to shift my own priorities and 
invest more hours. Though I admit that I'd have to bootstrap more Mavin to 
address these specific issues  properly; I have maintained Mavin builds but 
haven't written a nontrivial one de novo. And as I say, some of those jarfiles 
are themselves not in Mavin; there's at least one whose origin we're not 
completely sure of and a direct replacement may not exist.




--
   /_  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: Vladimir Sitnikov <sitnikov.vladi...@gmail.com>
Sent: Sunday, May 14, 2023 10:48:54 AM
To: dev@xalan.apache.org <dev@xalan.apache.org>
Subject: Re: Update of xalan 2.7.3 at Maven Central repository wiped metadata 
for previous versions from maven-metadata.xml


https://repo.maven.apache.org/maven2/xalan/xalan/maven-metadata.xml

Stanimir> Currently

I see that 2.7.2 is not listed there, and I think it is an issue.

Vladimir
--
Vladimir

Reply via email to