Our great sponsors
-
Chips-n-Salsa
A Java library of Customizable, Hybridizable, Iterative, Parallel, Stochastic, and Self-Adaptive Local Search Algorithms
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
Important Note: Because of the way JitPack essentially builds a snapshot of your repository, even for release builds, the jitpack.yml must be present within the specific snapshot of your repository in order to apply. For example, for the library that this post is based upon, Chips-n-Salsa, the first release where the repository contains the configuration file is 5.0.1, so JitPack will fail to build any prior version, although earlier versions are available via Maven Central and GitHub Packages. Likewise, if you specify any commit hash prior to that of the commit where that configuration file was introduced, the JitPack build will also fail.
JitPack works a bit differently than most other Maven artifact repositories. For most Maven repositories, such as Maven Central or GitHub Packages, you first build the artifacts either locally on your own system, or perhaps as part of a CI/CD workflow (e.g., via GitHub Actions); and then after building your artifacts (e.g., various jar files of compiled class files, source code, documentation, etc) you deploy them to your chosen Maven artifact repository.
Related posts
- Deploying Java Artifacts to Multiple Maven Repositories with GitHub Actions
- How to Use the Maven Shade Plugin if Your Project Uses Java Platform Module System
- Ahead-of-time JitPack Builds with Custom GroupId via GitHub Actions
- JaCoCo coverage badges, PR coverage checks, and PR coverage comments, from GitHub Actions
- How to Enable DEV Post Embeds for Pages From Your Website