jkesselm commented on PR #110:
URL: https://github.com/apache/xalan-java/pull/110#issuecomment-1872644394
Reconciled with Master.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific
Reminder for those not familiar with the convention:
MUST/MUST NOT: Requirement. Deviation should be avoided if at all possible,
should/must be documented while it does exist, and correcting the deviation is
a high priority.
SHOULD/SHOULD NOT: Guideline. Often highly recommended, but
Vladimir Sitnikov Saturday, December 30, 9:04 AM
Thank you for the reminder that PMC is free to ignore the rules as they see fit.
Unjustified and inappropriate snark. If this was a Rule it would say Must. It's
a guideline, which Apache recognized could be deviated from, and the deviation
is
This is an automated email from the ASF dual-hosted git repository.
mukulg pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/xalan-site.git
The following commit(s) were added to refs/heads/master by this push:
new 571c9c35 specifying the updated status of
(sorry again. Phone keyboard.. )
And we would need to handle the distinction between things that we know are
working, and things that by design should work, but don't yet, as we have in
the test suite.
All of which is doable. None of which is currently at the top of my own
priorities. But
(keep hitting the wrong button, sorry)...
We would probably watch to rewrite them to be driven by todays standard test
frameworks,
--
/_ Joe Kesselman (he/him/his)
-/ _) My Alexa skill for New Music/New Sounds fans:
/ https://www.amazon.com/dp/B09WJ3H657/
Caveat: Opinionated old
Having said all that, I actually agree that the Xalan-j specific tests should
be moved into the main project. We would probably want to rewrite them to
--
/_ Joe Kesselman (he/him/his)
-/ _) My Alexa skill for New Music/New Sounds fans:
/ https://www.amazon.com/dp/B09WJ3H657/
Caveat:
See the rest of my response.
Xalan-test inclusion in xalan-source was a courtesy to the folks fetching that
package, permitting functional verification of a correct build. I actually
agree with you that such isn't absolutely necessary, which is why I suggested
dropping that and telling folks
(sorry...)
... the original intent and design of XALAN-TEST is to be a general XSLT
standards compliance suite as much as (or more than) tests for the Xalan-J
implementation alone. As such, it was a semi-independent project that could be,
and was, configured to validate other implementations
>First, remember that SHOULD is not MUST, and that one of the distro files
(bin) is already fully compiled code and carries the binary dependencies to
run it, by design and decades-long history
Thank you for the reminder that PMC is free to ignore the rules as they see
fit.
A decade-long bad
Hi, Vlad. First, remember that SHOULD is not MUST, and that one of the distro
files (bin) is already fully compiled code and carries the binary dependencies
to run it, by design and decades-long history. That isn't going to change.
Second, remember that the original intent
--
/_ Joe
[
https://issues.apache.org/jira/browse/XALANJ-2723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mukul Gandhi resolved XALANJ-2723.
--
Resolution: Fixed
I'm marking this jira issue as resolved, since implementation for this jira
Mukul Gandhi created XALANJ-2723:
Summary: Implementation of xpath 3.1 function fn:deep-equal, for
XalanJ's interpretive processor
Key: XALANJ-2723
URL: https://issues.apache.org/jira/browse/XALANJ-2723
mukulga merged PR #146:
URL: https://github.com/apache/xalan-java/pull/146
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail:
mukulga opened a new pull request, #146:
URL: https://github.com/apache/xalan-java/pull/146
(no comment)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe,
15 matches
Mail list logo
