Tink Java has 4 Maven artifacts, all are in the
tink: this is the core of Tink built for server side apps. It only depends on
tink-android: this is similar to
tink but is built for Android apps. It only depends on
tink-awskms: this is a plugin for the
tink artifact that integrates Tink with AWS KMS.
tink-gcpkms: this is a plugin for the
tink artifact that integrates Tink with GCP KMS.
This command publishes latest snapshots to Maven, and their Javadocs to https://google.github.com/tink.
Snapshots are also automatically published for every new commit to the master branch of https://github.com/google/tink.
New snapshots are also automatically tested for every new commit to the master branch of https://github.com/google/tink.
This should be considered only when there is no other option, 'cause adding dependency makes Tink bloated and less secure. If a dependency got tampered with, Tink would also be affected.
This process consists of 3 steps:
To add a dependency for an artifact, you add it to the artifact's
pom.xml. For example, the
com.google.crypto.tink:tink artifact uses
tink.pom.xml. You should always depend on the latest version of the dependency on Maven Central.
Next, you want to publish a new snapshot of the artifact with the new dependency.
Then you want to test the new snapshot.
You want to repeat these steps until there is no error.
If you encounter
Dependency convergence error, it means that the artifact has already, usually indirectly, depended on another version of the new dependency. You want to exclude that version.
See the history of the POM files for examples.