[
https://issues.apache.org/jira/browse/XALANJ-2651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18014445#comment-18014445
]
Joe Kesselman commented on XALANJ-2651:
---------------------------------------
Turns out that xalan-java's ant build did *not* automatically invoke
xalan-test, though it had convenience targets for doing so. It just bundled the
current state of the sibling xalan-test into the source archive with whatever
outputs had last been seen, which might not fully match the code.
Hence I think we can move automatically running xalan-test into a separate task.
I'll comment out the work I've done on that (retaining it and a comment
spelling out the issue as documentation), commit, test, and if clean I'll
submit a pull request so we can close out _this_ task.
> 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
