Planning a Release of AntUnit

Hi all

while working on the CycloneDX Antlib I realized I missed the negation
of some assertions, assertPropertyNotSet for example.

When I added that I realized Matt has added a really nice feature four
years ago that we never release - nested <classpath> for AntUnit. With
this I can download AntUnit during the build and run the AntUnit task
after typedeffing it - but my tasks themselves don't need to know where
AntUnit is. I.e. the two typedefs in
https://github.com/apache/ant-antlibs-cyclonedx/blob/main/src/tests/antunit/shared.xml#L25
can be removed completely and the tests can load AntUnit and the
CycloneDX tasks just by declaring the namespaces.

I'd like to get this out - and of course add an SBOM while I'm at it :-)

Any thoughts?

    Stefan