Maven Dependency Tree Cleanup: Eliminates Bloat, Abandoned Libraries, and Security Risks

A significant Maven dependency cleanup has targeted a bloated and potentially insecure build environment. The effort directly confronts accumulated technical debt, removing abandoned libraries with known vulnerabilities, redundant binaries that inflate download sizes, and resolving version conflicts that plague the consumer classpath. This is not a minor refactor but a surgical strike on the highest-priority items from a long-standing cleanup backlog, addressing core stability and security concerns.

The changes, implemented in the project's `pom.xml`, are multi-faceted. To drastically reduce download size, the monolithic `jave-all-deps` artifact was replaced with `jave-core` and OS-specific profiles. This eliminates seven unnecessary platform-specific FFmpeg JARs from every consumer download, with profiles auto-activating to pull only the single matching native binary. Simultaneously, vulnerable and abandoned libraries were purged. The outdated `com.jcraft:jsch:0.1.55` was swapped for the API-compatible, maintained fork `com.github.mwiede:jsch:0.2.21`. The deprecated `json-simple` library was completely removed, with all usages migrated to the already-present Jackson framework.

This cleanup signals a move away from fragile, outdated dependencies that introduce security risks and maintenance burdens. By removing artifacts like the obsolete `mime-util` library and eliminating redundant plugin JARs, the project reduces its attack surface and streamlines the build process. The resolution of version conflicts further stabilizes the classpath, mitigating runtime errors and unpredictable behavior for downstream consumers. This systematic pruning is a critical step in hardening the project's foundation and improving long-term maintainability.