SDK / framework uplift

Full workflow

Complete guide (limitations, CI, published lens): sdk-uplift

Why use CCE

Major SDK upgrades (AWS v1 → v2, Spring Cloud AWS legacy → io.awspring.cloud, javax → jakarta) stall when nobody knows how many call sites remain. Spreadsheets and dependency scans show imports, not invocations.

CCE inventories every mapped SDK call site so migration teams can prioritize by volume, file, and module.

Example command

cce -folder . -language AUTO -mapper-file https://releases.stackgen.com/cce/lenses/sdk-uplift/latest/sdk-uplift_lenses.yaml -filter cloud -format json -output sdk-uplift.json

Analysis recipe

This use case is registered as recipe sdk-uplift — run with:

cce run -folder . -language AUTO -recipes sdk-uplift -output sdk-uplift.json

Published lens

https://releases.stackgen.com/cce/lenses/sdk-uplift/latest/sdk-uplift_lenses.yaml