tree: 4ff3f75b0dd48660eb9497b91d3b0f9855f3bba8 [path history] [tgz]
  1. apps-paymentmethodtoken.pom.xml
  2. apps-rewardedads.pom.xml
  3. apps-webpush.pom.xml
  8. settings.xml
  10. tink-android.pom.xml
  11. tink-awskms.pom.xml
  12. tink-gcpkms.pom.xml
  13. tink.pom.xml

Tink Java on Maven

Tink Java has 4 Maven artifacts, all are in the group.


The core of Tink built for server-side applications. It only depends on and


Similar to tink but is built for Android applicationss.

This build includes an embeded copy, which is renamed to be This is done to avoid dependency conflicts with other common dependencies that depend on a conflicting version (e.g. Firebase).


A plugin for the tink artifact that integrates Tink with AWS KMS.


A plugin for the tink artifact that integrates Tink with GCP KMS.

Publishing snapshots


This command publishes latest snapshots to Maven, and their Javadocs to

Snapshots are automatically published for every new commit to the master branch of

Testing snapshots


New snapshots are also automatically tested for every new commit to the master branch of

Adding a dependency

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:

  1. To add a dependency for an artifact, you add it to the artifact's pom.xml. For example, the artifact uses tink.pom.xml. You should always depend on the latest version of the dependency on Maven Central.

  2. Next, you want to publish a new snapshot of the artifact with the new dependency.

  3. 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.