Spike: Extract swift package information from lock file
Summary - Why is this spike needed?
This spike is needed to evaluate and compare the functionality, usability, and effectiveness of familiar package managers for Swift. By conducting this spike, we can determine which package manager best suits our project's requirements for dependencies scanning, ease of integration into our development workflow, and compatibility with our existing tools and infrastructure. The spike lets us decide which package manager to adopt, ensuring we extract the package and dependencies information for our customer Swift projects efficiently and effectively.
Tested PMs
Tasks to Evaluate for PM
-
Does the package manager generate a lock file, or which file does he use? -
Does the package manager create a lock file with a constant version? -
Does the package manager create the lock file in the build process? -
What must the customer do if he doesn't have the lock file? documentation
Links/References
Edited by Miki Amos