[
https://issues.apache.org/jira/browse/XALANJ-2822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18014449#comment-18014449
]
Joe Kesselman commented on XALANJ-2822:
---------------------------------------
Branch [https://github.com/apache/xalan-java/tree/XALANJ-2822] created; has
comments that document this issue, and commented-out Maven to cross-invoke ant
build for ../xalan-test, which should be useful for either the proper or
improper solutions proposed.
> Old issue: Packaging possibly outdated xalan-test result files
> --------------------------------------------------------------
>
> Key: XALANJ-2822
> URL: https://issues.apache.org/jira/browse/XALANJ-2822
> Project: XalanJ2
> Issue Type: Bug
> Security Level: No security risk; visible to anyone(Ordinary problems in
> Xalan projects. Anybody can view the issue.)
> Components: Build, TestHarness-TestCase, Xalan
> Reporter: Joe Kesselman
> Priority: Minor
> Fix For: The Latest Development Code
>
>
> As of XALANJ-2651 , the maven build will emulate the old ant build's behavior
> and include a copy of ../xalan-test in the .src.tar.gz/.src/zip package files.
> {*}Issue, persisting from the Ant build{*}: That copy may include test result
> files that are out of date vs. the source code being packaged.
> Fixing this "properly" – ensuring that packaging always includes _successful,
> current_ test results -- would require modifying xalan-test to not depend on
> the un-version-numbered jarfiles we're producing in xalan-java/build, since
> those do not exist until packaging has run. That would seem to require either
> having xalan-test determine the version number being tested and use that in
> its classpaths, or changing xalan-test to reference ../xalan-java/target/*
> since that's the only form of wildcard Java allows in classpaths.
> Fixing it "improperly" would just require ensuring that test results are not
> present in the source bundles, so we don't risk lying to the user about the
> current xalan-test status. Currently xalan-test does not have a target that
> cleans out old test results, but one could be added, and that could be
> invoked without requiring we find the current xalan-java.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
