fix(adobemedia): write resolved dependency versions into POM and re-include in publish

[denischilik]

Background

adobemedia-3 resolves its Adobe Experience Platform extensions through the com.adobe.marketing.mobile:sdk-bom (declared with a version range), so the individual extensions (core, analytics, media, userprofile, lifecycle, identity, signal) are declared without explicit versions — the BOM supplies them at build time.

The generated Maven POM therefore listed those dependencies with an empty <version>. Maven Central rejects version-less dependencies (Dependency version information is missing for dependency: com.adobe.marketing.mobile:core, …), and because Central Portal deployments are atomic, that single failure blocked the entire kits bundle. As a stopgap, #739 excluded adobemedia-3 from the 6.0.0 publish.

What changed

• kits/adobemedia/adobemedia-3/build.gradle — add a versionMapping block (scoped to this module only) that maps each published dependency to the version resolved on the releaseCompileClasspath / releaseRuntimeClasspath. The published POM now carries concrete versions while build.gradle keeps the readable sdk-bom range (auto-tracking 3.x, parity with the iOS SPM .upToNextMajor(from: "3.0.0")).
• settings-kits.gradle, kits/matrix.json, settings-kit-examples.gradle — reverse the chore: exclude adobemedia-3 from 6.0 publish and enable manual publish trigger #739 exclusion so the kit is built, tested, and published again.

No VERSION change here — the fix ships in the next release bump (Release – Draft), so the full kits bundle re-publishes at a fresh version with adobemedia-3 included.

Validation

Generated the POM locally and confirmed every dependency now has a concrete version:

sdk-bom     -> 3.20.0 (import)
core        -> 3.8.0
analytics   -> 3.0.2
media       -> 3.1.2
userprofile -> 3.0.1
lifecycle   -> 3.0.2
identity    -> 3.0.2
signal      -> 3.0.1

./gradlew -c settings-kits.gradle :kits:android-adobemedia:adobemedia-3:generatePomFileForMavenPublication -PVERSION=6.0.0 → no version-less <dependency> entries remain.

Test plan

• CI: build-kits matrix runs :kits:android-adobemedia:adobemedia-3:testRelease green.
• Next release publishes com.mparticle:adobemedia-3 to Maven Central (POM validation passes).

[cursor]

PR Summary

^{Cursor Bugbot is generating a summary for commit 6120f1e. Configure here.}

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud