I'd be perfectly happy to see us put out a 2.7.3.1 release with this patched, if someone knows exactly what changes need to be made. Or even 2.7.4.
It's legitimately a release bug. -- /_ 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: Gary D. Gregory (Jira) <j...@apache.org> Sent: Thursday, July 20, 2023 9:59:00 AM To: dev@xalan.apache.org <dev@xalan.apache.org> Subject: [jira] [Commented] (XALANJ-2644) Publish xalan 2.7.3 to Maven central repository [ https://issues.apache.org/jira/browse/XALANJ-2644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17745099#comment-17745099 ] Gary D. Gregory commented on XALANJ-2644: ----------------------------------------- IIRCI, once a file is published then that's it, you can't change it, that will be for the next release. > Publish xalan 2.7.3 to Maven central repository > ----------------------------------------------- > > Key: XALANJ-2644 > URL: https://issues.apache.org/jira/browse/XALANJ-2644 > Project: XalanJ2 > Issue Type: Improvement > Security Level: No security risk; visible to anyone(Ordinary problems in > Xalan projects. Anybody can view the issue.) > Components: Xalan > Affects Versions: 2.7.3 > Reporter: Vladimir Sitnikov > Assignee: Steven J. Hathaway > Priority: Blocker > Labels: maven > > Please see XALANJ-2417 and do as was asked there for the current release. > IMHO this would greatly quicken the distribution of this security fix. > In this context please also consider XALANJ-2578 - that'd make life easier > for a lot of developers that depend on xalan. -- This message was sent by Atlassian Jira (v8.20.10#820010) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org For additional commands, e-mail: dev-h...@xalan.apache.org
