[
https://issues.apache.org/jira/browse/XALANJ-2651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18013524#comment-18013524
]
Joe Kesselman commented on XALANJ-2651:
---------------------------------------
Still too discursive, but:
1) Trick to calling xalan-test ant build from integration-test/pom.xml is to
use the maven-antrun-plugin and have its target issue a <subant> task to invoke
the xalan-test/build.xml. The <ant> task might work, but <subant> has more
useful features, including switches for `failonerror` and `verbose`
2) Unfortunately that isn't quite working right yet. The problem appears to be
that the xalan-test custom ant Tasks we use to analyze whether a test suite has
passed or failed (while excluding "accepted" failures, set in xalan-test's
properties file) are using relative directory paths, assuming that current
directory equals ant basedir... and when invoked this way, that isn't true.
Simplest fix seems to be to pass the absolute ${basedir} down to these Tasks so
they can turn relative paths into absolute. That shouldn't be complicated.
3) I'm not sure there's a target in xalan-test/build.xml that actually builds
these custom Tasks. It looks like they're just checked in and copied. That
should be fixed. Meanwhile, I'm building them by hand for testing.
> 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
