You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@xalan.apache.org by Joseph Kessselman <ke...@alum.mit.edu> on 2024/03/24 23:38:05 UTC
Still trying to get back to work on Xalan...
1) I'm still waiting/hoping for someone to remind me of how we release a
new version of Xalan. After all that work Mavenizing it, I'd like to see
us actually cut over... and it could also address some of the old gripes
about class conflicts and dependency delarations. Assuming I didn't make
_too_ much of a mess when porting the build over.
(There may still be some tweaking there to make sure all the fields
people want to see in the POM are being filled in correctly by the Maven
build. Need to find cycles to review those tasks.)
If release has happened, it must be possible....
2) I've posted a Jira work item for my suggestion that, if the XSLT3
prototype logic can cleanly be turned into Xalan Extensions, it could be
released as part of the Xalan Extension Library and thus start shipping
with base Xalan. Some of the EXSLT library was, in fact, early
prototypes of functions that XSLT3 would later provide, and provides
some illustration of how Xalan functions are written (and how we've
handled them in test). Downside is that it would require the new
functionality be accessed with namespace prefixes; upside is that it
would make the division between portable 2.0 and half-portable
3.x-subset much clearer, and would emphasize keeping changes to core
Xalan clean and isolated to minimize risk of regression in 2.0
compatibility.
I've assigned it to Mukul, but others may want to weigh in on what
priority this should be given and/or whether it's worth doing at all.
3) My time is still going to be erratically available for the next 4
weeks at least, due to a series of personal commitments. But I do want
to get Xalan back onto an actual release cycle, and make enough progress
whittling down the backlog to justify regular releases.
--
` /_ 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. Feel free to call him on it.
Re: Still trying to get back to work on Xalan...
Posted by Mukul Gandhi <ga...@gmail.com>.
Hi Joseph,
On Mon, Mar 25, 2024 at 5:09 AM Joseph Kessselman <ke...@alum.mit.edu> wrote:
> 2) I've posted a Jira work item for my suggestion that, if the XSLT3
> prototype logic can cleanly be turned into Xalan Extensions, it could be
> released as part of the Xalan Extension Library and thus start shipping
> with base Xalan. Some of the EXSLT library was, in fact, early
> prototypes of functions that XSLT3 would later provide, and provides
> some illustration of how Xalan functions are written (and how we've
> handled them in test). Downside is that it would require the new
> functionality be accessed with namespace prefixes; upside is that it
> would make the division between portable 2.0 and half-portable
> 3.x-subset much clearer, and would emphasize keeping changes to core
> Xalan clean and isolated to minimize risk of regression in 2.0
> compatibility.
>
> I've assigned it to Mukul, but others may want to weigh in on what
> priority this should be given and/or whether it's worth doing at all.
Just few quick thoughts from me.
I'll be happy and willing to remove my @author name from all Xalan
xslt 3.0 and corresponding tests code that I've written on Xalan dev
repos branch xalan-j_xslt3.0. May be that, may help others little but
more willing to consider those code files that I've written to view,
review and possibly to be modified by other Xalan committers. I'm fine
to have my @author name removed or retained as they're currently
written within specific Xalan code files.
My other naive feeling is that, we should keep maintaining for long
term Xalan dev repos branches master (which should have XSLT 1.0
implementation) and xalan-j_xslt3.0 (which should have in-progress
XSLT 3.0 implementation).
I'll (or, anyone else as well from Xalan community) as well be happy
and willing to modify XSLT 3.0 and XPath implementation code on the
Xalan dev repos branch xalan-j_xslt3.0 as per any implementation or
quality feedback from anyone within Xalan community.
Please advise.
--
Regards,
Mukul Gandhi
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@xalan.apache.org
For additional commands, e-mail: dev-help@xalan.apache.org