[
https://issues.apache.org/jira/browse/XALANJ-2651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17814958#comment-17814958
]
Joe Kesselman commented on XALANJ-2651:
---------------------------------------
Folding xalan-test into Xalan should be a separate Jira task, and needs
discussion; see past comments in the developers mailing list.
xalan-test was intended to be usable to test Xalan-J, xalan-c, and other
processors other processors. Well some of it's tests are specific to xalan,
most of them are conformance tests against the standard rather than our
specific code. Although we have moved the C++ code to the Apache attic, the
generality of these tests still remains, and is still an argument for keeping
them separate.
Also, the current test drivers are fairly tightly integrated with Apache at.
Migrating the tests to work with the new maven-based build for xalan-j could be
complicated. Of course, as a short-term measure, we can have the maven build
invoke the ant build, but that's a bit ugly.
Also, it can be argued that what the Java source package really needs is an
entirely new suite of unit tests, rather than the functional and integration
tests provided by the current test package. So that would be a huge task, and
for immediate purposes might be a case of boiling the ocean to make a cup of
tea.
So there are decisions to be made here, And discussing that kind of direction
is generally a function of the mailing list rather than jira tasks. The task is
more about the details of how, where the mailing list addresses what and why.
It's a worthwhile question. But _this_ jira task is not the right place to dive
into it. Open a new one, or bring it up in the mail list. Or both.
We still need to address the question of whether a copy of the test suite will
ship with the source bundles. Historically, we have included it, and we
probably should continue to do so. However, that has not yet been integrated
into the maven build. I don't have the cycles for it right now, but I would
like to see that resolved one way or another before closing out this work item.
> 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
