Maven integration
Protection belongs in the release process.
One release workflow#
Download the Maven integration and matching annotation package from Client Area → Downloads. Use the coordinates and version supplied with that release. The distributed integration authenticates with the protection service; it does not ship the private transformation engine. Keep credentials in your build environment’s secret store, outside the POM and repository.
Compile. Protect. Verify.#
Compile your application with the annotation library as a provided dependency, so the build directives are available without bundling the engine. Run protection after the JAR has been packaged. Preserve the original artifact, attach the protected artifact separately, and make release publication depend on successful protection and validation.
Built for repeatable releases#
- Pin the integration, annotation package and selected protection profile for each release.
- Keep mappings and diagnostics private. Retain the build identifier when contacting Support.
- An unavailable service or failed protection must stop publication, not silently release the original JAR.