[
https://issues.apache.org/jira/browse/XALANJ-2651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18013007#comment-18013007
]
Joe Kesselman edited comment on XALANJ-2651 at 8/9/25 7:03 PM:
---------------------------------------------------------------
It occurs to me that the advantage of copying xalan-test with whatever files
the user may have added or modified, rather than pulling a fresh copy, is that
the result files will be picked up. Which, if the results are current, would be
documentation of test status.
Or I could make the distribution build actually run the tests, to make sure
that is reasonably current. Which is probably cleaner, though slower.
was (Author: JIRAUSER285361):
It occurs to me that the advantage of copying xalan-test with whatever files
the user may have added or modified, rather than pulling a fresh copy, is that
the result files will be picked up. Which, if the results are current, would be
documentation of test status.
Could make the distribution build actually run the tests, to make sure that is
reasonably current.
> Migrate build from Ant to Maven
> -------------------------------
>
> Key: XALANJ-2651
> URL: https://issues.apache.org/jira/browse/XALANJ-2651
> Project: XalanJ2
> Issue Type: Improvement
> Security Level: No security risk; visible to anyone(Ordinary problems in
> Xalan projects. Anybody can view the issue.)
> Components: Build
> Reporter: Gary D. Gregory
> Assignee: Joe Kesselman
> Priority: Major
>
> Migrate the build from Ant to Maven.
--
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
