[reckart]

What's in the PR

• Move the binary distribution build out of the root aggregator into a new uimaj-dist module, relocating the assembly descriptor, launch scripts, logger properties, readme helper scripts and binary-distribution LICENSE/NOTICE files along with the bundled-artifact dependency list that defines the archive contents
• Restore the maven-deploy-plugin skip explicitly on the root, which was previously inherited from the parent-pom build distribution profile that activates on the presence of src/main/assembly/bin.xml
• Declare jVinci, jackson-core and commons-lang3 as direct dependencies of the distribution instead of relying on them arriving transitively, so the shipped lib/ no longer depends on another module's dependency graph
• Drop the log4j bindings from the distribution and document that it ships exactly one slf4j binding, since a second binding on the launcher classpath would silently disable the bundled logger configuration
• Force the root aggregator to build before uimaj-dist via an explicit dependency, as the aggregated Javadoc and generated release notes can only be produced on the root but are consumed by the binary assembly
• Add a check-distribution-inputs guard that fails release builds fast when the aggregated Javadoc or release notes are missing, rather than silently producing an archive with empty sections
• Move all RC auto-staging into uimaj-dist by relocating the marker-file-enabling-auto-staging marker, so the staging timestamp and candidate id are generated and consumed in one module and the binary distribution, source release and Eclipse update site all land in a single correctly named staging folder
• Stage the source-release archive alongside the binary distribution, which was no longer being picked up after the move because the two archives now live in separate target directories
• Assert that both archives are present in the staging folder, as Ant treats a fileset matching nothing as success and would otherwise publish an incomplete release candidate
• Override the staging folder name and SCM commit message so the release candidate is named after the product rather than the new module's artifact id
• Fix an unless:set="iisApacheRelease" typo that prevented the non-release-build staging message from ever being emitted
• Add .mvn/maven.config forcing the depth-first dependency collector, working around a thread-safety bug in the p2 layout resolver extension under Maven 4
• Exclude a gitignored scratch/ directory from RAT checks and from the source-release assembly, as that assembly packages the working directory rather than the git index
• Update the release and Eclipse setup documentation for the relocated paths, and correct the stale project name in the Eclipse launch configuration for the source-packaging script

How to test manually

• No specific test procedure

Automatic testing

• PR adds/updates unit tests

Documentation

• PR adds/updates documentation

Organizational

• PR adds/updates dependencies.
  _{^{Only dependencies under approved licenses are allowed. LICENSE and NOTICE files in the respective modules where dependencies have been added as well as in the project root have been updated.}}