fix: declare explicit dependency on jackson-annotations2-api

[M0Rf30]

Summary

Fixes a java.lang.LinkageError (loader constraint violation) that prevents JfStep from initializing on Jenkins controllers running jackson2-api 2.19 or newer.

Problem

Starting with jackson2-api 2.19, the plugin was split: jackson-annotations was moved into a separate jackson-annotations2-api Jenkins plugin. The jfrog plugin still declares a dependency only on jackson2-api, so com.fasterxml.jackson.annotation.JsonInclude$Include is visible to BuildInfoExtractorUtils via one PluginClassLoader and to ObjectMapper.setSerializationInclusion(...) via another.

When JfStep.<clinit> calls BuildInfoExtractorUtils.createMapper the JVM sees two different Class objects for the same FQN and refuses method resolution:

java.lang.LinkageError: loader constraint violation: when resolving method
'com.fasterxml.jackson.databind.ObjectMapper
 com.fasterxml.jackson.databind.ObjectMapper.setSerializationInclusion(
  com.fasterxml.jackson.annotation.JsonInclude$Include)'
the class loader 'PluginClassLoader for jfrog'  ... and the class loader
'PluginClassLoader for jackson2-api' ... have different Class objects for
the type com/fasterxml/jackson/annotation/JsonInclude$Include ...
    at org.jfrog.build.extractor.BuildInfoExtractorUtils.createMapper(...:341)
    at io.jenkins.plugins.jfrog.JfStep.<clinit>(JfStep.java:46)

Fix

Declare io.jenkins.plugins:jackson-annotations2-api explicitly in pom.xml. The maven-hpi-plugin then emits it inside the Plugin-Dependencies manifest entry so Jenkins delegates annotation class loading through the same loader jackson2-api uses.

The dependency is pinned because the current bom-2.462.x does not manage jackson-annotations2-api yet.

Verification

Rebuilt plugin. The resulting HPI manifest now contains both plugin dependencies:

Plugin-Dependencies: ..., jackson-annotations2-api:2.21-7.v4777af3aad47,
 ..., jackson2-api:2.21.2-433.v6d50b92cfe52, ...

After installing the patched HPI on the affected controller the LinkageError no longer occurs and jf pipeline steps run as before.

Fixes #150

Test plan

• CI builds the plugin
• Install the resulting HPI on a Jenkins controller that has jackson2-api >= 2.19
• Run a pipeline that uses tools { jfrog 'jfrog-cli' } and confirm JfStep initializes without a LinkageError

[github-actions]

CLA Assistant Lite bot All contributors have signed the CLA ✍️ ✅

[M0Rf30]

I have read the CLA Document and I hereby sign the CLA