Hi, Vlad. First, remember that SHOULD is not MUST, and that one of the distro files (bin) is already fully compiled code and carries the binary dependencies to run it, by design and decades-long history. That isn't going to change.
Second, remember that the original intent -- /_ Joe Kesselman (he/him/his) -/ _) My Alexa skill for New Music/New Sounds fans: / https://www.amazon.com/dp/B09WJ3H657/ Caveat: Opinionated old geezer with overcompensated writer's block. May be redundant, verbose, prolix, sesquipedalian, didactic, officious, or redundant. ________________________________ From: Vladimir Sitnikov <sitnikov.vladi...@gmail.com> Sent: Saturday, December 30, 2023 2:01:02 AM To: dev@xalan.apache.org <dev@xalan.apache.org> Subject: Re: Policy question re src distribution >In the past, the src tarball/zipfile has included an embedded copy of >xalan-test Please review the release policy https://www.apache.org/legal/release-policy.html#source-packages In particular, they say "A source release SHOULD not contain compiled code". As xalan-test contains many jars with compiled code, you should rather NOT include xalan-test in its current shape into xalan-java source packages. At the same time, they say "Each PMC MUST obey the ASF requirements on approving any release." >Or should xalan-test have its own distros? That would be overhead without much benefit. It would be better to integrate tests into xalan-java code eventually. Vladimir
