Currently tarballs are downloaded to a temp directory and then automatically cleaned up.
This doesn't help in cases where we want to create an Artifactory "build info" that lists the bower dependencies for the current build.
Assuming that each (CI) build runs with a unique cache via --config.storage.cache or similar, save downloaded tarballs to cache to allow further inspection (get sha1, md5, etc).
In order to provide backwards compatibility, maybe bower-art-resolver can use a .bowerartrc (or similar) to control behavior and cache paths.
Currently tarballs are downloaded to a temp directory and then automatically cleaned up.
This doesn't help in cases where we want to create an Artifactory "build info" that lists the bower dependencies for the current build.
Assuming that each (CI) build runs with a unique cache via
--config.storage.cacheor similar, save downloaded tarballs to cache to allow further inspection (get sha1, md5, etc).In order to provide backwards compatibility, maybe
bower-art-resolvercan use a.bowerartrc(or similar) to control behavior and cache paths.