jkesselm commented on PR #110:
URL: https://github.com/apache/xalan-java/pull/110#issuecomment-1792965952
Another current difference between the ant and maven builds is how the
"distribution" archives are created.
Currently, the ant build generates both zip and .tar.gz versions of
xalan-j_version_number-bin.tar and xalan-j_version_number-src.tar.
The Ant source collection puts everything under a top-level
xalan-j_version_number/ directory, and pulls xalan-test in as a subdirectory.
The intent appears to be to facilitate atomic distribution, build, and test
when fetch from git is not practical. Maven instead is currently producing a
.sources.jar for each module, and is not including the tests in any of them
(though it will do so if/when we migrate xalan-test into xalan_java/test). Is
there still a need for a source distribution collection?
The Ant bin collection does *not* include a copy of the tests, but does
bundle xalan and serializer under a xalan-j_version_number/ directory, and
includes documentation and SOURCE of the samples -- in other words, it's
basically the build output minus compilation of the samples. It does *not*
bundle the tests. Maven is not currently producing an equivalent. Is there
still a need for this?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org
For additional commands, e-mail: dev-h...@xalan.apache.org
