[
https://issues.apache.org/jira/browse/XALANJ-2711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18014447#comment-18014447
]
Joe Kesselman commented on XALANJ-2711:
---------------------------------------
See xalan-java branch XALANJ-2711 for stub work to support this – code sketch
of how to invoke xalan-test's ant build, currently commented out.
We should create a xalan-test branch with the same name if/when changes are
needed there.
> Test improvements: Remove/deprecate endorsed/bootclasspath kluges
> -----------------------------------------------------------------
>
> Key: XALANJ-2711
> URL: https://issues.apache.org/jira/browse/XALANJ-2711
> Project: XalanJ2
> Issue Type: Improvement
> Security Level: No security risk; visible to anyone(Ordinary problems in
> Xalan projects. Anybody can view the issue.)
> Components: TestHarness-TestCase
> Reporter: Joe Kesselman
> Assignee: Joe Kesselman
> Priority: Major
>
> Back in the days before Java 1.5, Sun had a bad habit of simply copying the
> Apache code directly into their own library jarfiles. Since those were on the
> bootclasspath, some moderately obscene workarounds were needed if you wanted
> to run a version from Apache; you had to shoehorn the apache jars into the
> front of bootclasspath, or use the --endorsedlib mechanism which did
> basically the same thing. It was never a good solution; Sun had just made
> using anything but their snapshot of Apache code obscenely difficult.
> But around Java 1.5 everyone agreed to standardize upon the JAXP/TrAX "plug
> in" APIs as the portable way to invoke XML parsers, XPaths, and XSLT, and
> Sun/Oracle moved their ships-with-java snapshot of the Apache code down into
> com.sun.org.apache where it doesn't collide with "real" Apache releases.
> The test driver is still set up for the days before JAXP/TrAX. We noticed
> this when working with property retrievals in proposed changes to the Version
> classes; it's necessary to check both classloader and bootclassloader to
> cover both without and with the kluge.
> I propose that we drop, or at least deprecate, Xalan loading on the
> bootclasspath, and consider removing that hack from the xalan-test drivers.
> We may need to continue to support (and test?) running in that mode for one
> release, with a warning issued on stderr, to convince customers to follow up
> into the modern era, but I think it's time we started trying to leave that
> behind us.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
