You can now upload and distribute arbitrary files via Cloudsmith Maven repositories, whether pulled from upstream sources or directly uploaded.
Previously we supported artifacts that were using well known file names (Maven coordinates). As Maven doesn't enforce any standard when uploading a filename, we were not proxying and caching non-standard files from upstream repositories, nor supporting the direct upload of those non-standard files. Now, if you depend on non-standard Maven file names (such as custom dependencies or miscellaneous files) you can cache these from upstream repositories, as well as upload directly to Cloudsmith.
What’s Changed?
Cloudsmith has expanded support for the Maven format to include arbitrary (non-standard) files. These are files that don’t follow the typical Maven artifact structure but are still versioned and distributed using Maven-compatible tooling.
These include:
- .zip, .tar.gz, .exe, .dmg and other binary assets
- Configuration files, templates, and scripts
- Documentation bundles
- Any other file that doesn’t require strict Maven packaging
Arbitrary file support applies to:
- Upstream repositories: Files outside the conventional structure are now proxy, cached and served from upstream repositories.
- Direct uploads: You can now attach arbitrary files during a package upload. Our support includes -
- Uploading using Maven, Gradle, and SBT native tooling
- Uploading using the Cloudsmith API and CLI
Check out our Maven Repository documentation for more information, or contact us if you have questions or feedback on these new capabilities.