Hi Gary, I believe that, XalanJ is a pretty nice project, and useful to programming community in various circumstances. I personally, use XalanJ from time to time, even these days. Currently, I frequently use, XalanJ's XPath 1.0 engine for various kinds of work. XalanJ's XSLT 1.0 implementation, is awesome as well, and I use that occasionally as well these days.
I've thought over the past couple of days over this topic, since I saw your original mail within this thread, suggesting to move XalanJ to Attic. IMHO, I feel that, XalanJ should not move to Attic sometime soon. Even if, XalanJ developers have not been much active over the last couple of months or years, I believe that, XalanJ project should be active at Apache, for the benefit of XML and XSLT community and for those who integrate XalanJ within their applications. If I may compare, XSLT 1.0 to something as awesome as C language, despite many newer and widely adopted language these days, likeness of C language within the programming community hasn't reduced, and still C language is used whenever its needed. I believe that, the same holds true for XSLT 1.0 as well. On Wed, Jul 13, 2022 at 5:26 PM Gary Gregory <garydgreg...@gmail.com> wrote: > > Hello All, > > Let us consider retiring the Apache Xalan project to the Attic, or at > least its Xalan-J component. > > While it saddens me that I've not taken the time to continue > maintaining this project, I see the following: > - No one remembers or knows _for sure_ how to release components like > Xalan-J, specifically what svn, now git branches are for what. I did > the last Xalan-J release a long time ago and it would take a lot of > effort to gather up the pieces to do another, and Xalan-J should > really have a maintenance release. I don't want to take my FOSS time > to do this ATM. > - I have pinged this very list in the past for help on building > Xalan-J and received zero feedback, so I can only conclude that, aside > from me for the Xalan-J side at least, there is no institutional > knowledge left. > - There are a number of Xalan-J Jira tickets that have been left dying > on the vine, some with patches even. > - Very little if any Xalan-J user activity, which might be > self-fulfilling due to project inactivity > - On the Xalan-C side, there has been some activity so there might be > hope there. I've never worked on the Xalan-C component so I cannot say > anything about it. > - We could retire the Xalan-J component and keep Xalan-C alive, thus > keeping this PMC alive. > > What are your thoughts? > > Before you consider volunteering to perform a release, I would > encourage you to try locally, building a release is a lot more than > compiling a jar ;-) and there might not be anyone available to help > once you hit a snag, IOW, pitfalls, and time sink. > > Gary (PMC Chair) -- Regards, Mukul Gandhi --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org For additional commands, e-mail: dev-h...@xalan.apache.org
