jackson-base
Used in:
components
- OverviewOverview
- VersionsVersions
- DependentsDependents
- DependenciesDependencies
<dependency>
<groupId>com.fasterxml.jackson</groupId>
<artifactId>jackson-base</artifactId>
<version>2.21.0</version>
</dependency><?xml version="1.0" encoding="UTF-8"?>
<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
<modelVersion>4.0.0</modelVersion>
<parent>
<groupId>com.fasterxml.jackson</groupId>
<artifactId>jackson-bom</artifactId>
<version>2.21.0</version>
</parent>
<artifactId>jackson-base</artifactId>
<name>Jackson Base</name>
<packaging>pom</packaging>
<description>Parent pom for components of Jackson dataprocessor: includes base settings as well
as consistent set of dependencies across components. NOTE: NOT to be used by components outside
of Jackson: application code should only rely on `jackson-bom`
</description>
<licenses>
<license>
<name>The Apache Software License, Version 2.0</name>
<url>http://www.apache.org/licenses/LICENSE-2.0.txt</url>
<distribution>repo</distribution>
</license>
</licenses>
<properties>
<moditect.sourceGroup>${project.groupId}</moditect.sourceGroup>
<moditect.sourceArtifact>${project.artifactId}</moditect.sourceArtifact>
<moditect.sourceVersion>${project.version}</moditect.sourceVersion>
<!-- To fix [jackson-bom#52] need to first use better default version for
parent pom, and then also allow override as need be
-->
<jackson-bom.version>${project.parent.version}</jackson-bom.version>
<!-- for Reproducible Builds -->
<project.build.outputTimestamp>2026-01-18T21:50:21Z</project.build.outputTimestamp>
</properties>
<dependencyManagement>
<dependencies>
<!-- JPMS Libraries-->
<dependency>
<groupId>javax.activation</groupId>
<artifactId>javax.activation-api</artifactId>
<version>${javax.activation.version}</version>
</dependency>
<!-- Test dep versions -->
<dependency>
<groupId>org.assertj</groupId>
<artifactId>assertj-core</artifactId>
<version>${version.assertj}</version>
<scope>test</scope>
</dependency>
<!-- JUnit4 still used for many components (but not core) -->
<dependency>
<groupId>junit</groupId>
<artifactId>junit</artifactId>
<version>${version.junit}</version>
<scope>test</scope>
</dependency>
<!-- Starting to migrate to JUnit5 -->
<dependency>
<groupId>org.junit</groupId>
<artifactId>junit-bom</artifactId>
<version>${version.junit5}</version>
<type>pom</type>
<scope>import</scope>
</dependency>
</dependencies>
</dependencyManagement>
<build>
<pluginManagement>
<plugins>
<!-- Verify existence of certain settings
-->
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-enforcer-plugin</artifactId>
<executions>
<execution>
<id>enforce-java</id>
<phase>validate</phase>
<goals>
<goal>enforce</goal>
</goals>
<configuration>
<rules>
<requireMavenVersion>
<version>[3.6,)</version>
<message>[ERROR] The currently supported version of Maven is 3.6 or higher</message>
</requireMavenVersion>
<requirePluginVersions>
<banLatest>true</banLatest>
<banRelease>true</banRelease>
<banSnapshots>true</banSnapshots>
<phases>clean,deploy,site</phases>
<message>[ERROR] Best Practice is to always define plugin versions!</message>
</requirePluginVersions>
</rules>
</configuration>
</execution>
<execution>
<id>enforce-properties</id>
<phase>validate</phase>
<!-- important! Do NOT enable here since parent does not define, build would fail
BUT: alas means child has specify settings for phase AND goals like so:
<phase>validate</phase>
<goals>
<goal>enforce</goal>
</goals>
-->
<configuration>
<rules>
<!-- Needed both for Replacer plug-in AND for Automatic Module Name -->
<requireProperty>
<property>packageVersion.package</property>
</requireProperty>
<requireProperty>
<property>packageVersion.dir</property>
</requireProperty>
</rules>
</configuration>
</execution>
</executions>
</plugin>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-javadoc-plugin</artifactId>
<configuration>
<!-- Disable Java 8 javadoc warnings -->
<!-- 26-Mar-2018: Not for 2.9... (was left in for 2.9.5, alas)
<additionalparam>-Xdoclint:none</additionalparam>
-->
<!-- ... if on Java 8 -->
<!-- otherwise just: -->
<failOnError>false</failOnError>
<links>
<link>http://docs.oracle.com/javase/8/docs/api/</link>
</links>
</configuration>
</plugin>
<!-- Bind replacer execution (defined in `jackson-parent` for 2.x)
to "generate-sources" phase (see
https://avajava.com/tutorials/lessons/what-are-the-phases-of-the-maven-default-lifecycle.html
) by default; but do not trigger it (project still needs to add plugin
in build section)
-->
<plugin>
<groupId>com.google.code.maven-replacer-plugin</groupId>
<artifactId>replacer</artifactId>
<executions>
<execution>
<id>process-packageVersion</id>
<phase>generate-sources</phase>
</execution>
</executions>
</plugin>
<!-- 28-Apr-2025, tatu: Add SBOM generation support [JSTEP-14] -->
<plugin>
<groupId>org.cyclonedx</groupId>
<artifactId>cyclonedx-maven-plugin</artifactId>
<configuration>
<classifier>sbom-cyclonedx</classifier>
<!-- 16-Nov-2025, tatu: Should not skip because new Deploy mechanism
`central-publishing-maven-plugin` NOT consider "deploy" apparently
-->
<skipNotDeployed>false</skipNotDeployed>
</configuration>
<!-- 16-Nov-2025, tatu: We will NOT need "makeAggregateBom" for
any projects since Jackson multi-module projects have
parent poms only, not true aggregation
-->
<executions>
<execution>
<phase>package</phase>
<goals><goal>makeBom</goal></goals>
</execution>
</executions>
</plugin>
<plugin>
<groupId>org.moditect</groupId>
<artifactId>moditect-maven-plugin</artifactId>
<executions>
<execution>
<id>add-module-infos</id>
<phase>package</phase>
<goals>
<goal>add-module-info</goal>
</goals>
<configuration>
<overwriteExistingFiles>true</overwriteExistingFiles>
<module>
<moduleInfoFile>src/moditect/module-info.java</moduleInfoFile>
</module>
</configuration>
</execution>
</executions>
<!-- 22-Feb-2021, tatu: For Jackson 2.13+, put `module-info.class`
under "META-INF/versions/11" (instead of root, /); helps pre-Java9
libraries, frameworks, as well as avoids warnings by tooling
-->
<!-- 27-Jan-2022, tatu: as per [databind#3380] etc, really need to use
"META-INF/versions/9" for tooling compatibility
-->
<configuration>
<jvmVersion>9</jvmVersion>
</configuration>
</plugin>
<plugin>
<groupId>org.gradlex</groupId>
<artifactId>gradle-module-metadata-maven-plugin</artifactId>
<version>1.2</version>
<executions>
<execution>
<goals>
<goal>gmm</goal>
</goals>
</execution>
</executions>
<configuration>
<!-- When multiple Jackson modules of different versions are combined through transitive dependencies,
the following configuration ensures that the versions are aligned to the highest Jackson version in
the dependency graph.
For further details, refer to: https://blog.gradle.org/alignment-with-gradle-module-metadata -->
<platformDependencies>
<dependency>
<groupId>com.fasterxml.jackson</groupId>
<artifactId>jackson-bom</artifactId>
<version>${jackson-bom.version}</version>
</dependency>
</platformDependencies>
</configuration>
</plugin>
<!-- 03-Nov-2020, tatu: For 2.12, defaults for better LICENSE inclusion -->
<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>build-helper-maven-plugin</artifactId>
<executions>
<execution>
<id>add-resource</id>
<phase>generate-resources</phase>
<goals>
<goal>add-resource</goal>
</goals>
<configuration>
<resources>
<resource>
<directory>${project.basedir}</directory>
<targetPath>META-INF</targetPath>
<includes>
<include>LICENSE</include>
</includes>
</resource>
</resources>
</configuration>
</execution>
<!-- 04-May-2024, tatu: For [core#1264] need "cleansed" version
-->
<execution>
<id>regex-property</id>
<!-- default phase is "validate" as per https://www.mojohaus.org/build-helper-maven-plugin/usage.html
-->
<goals>
<goal>regex-property</goal>
</goals>
<configuration>
<name>project.version.underscore</name>
<value>${project.version}</value>
<regex>\.</regex>
<replacement>_</replacement>
<failIfNoMatch>true</failIfNoMatch>
</configuration>
</execution>
</executions>
</plugin>
<!-- 27-Nov-2022, tatu: [bom#56] Configure Felix-bundle and maven-jar plugins to
use fixed Timestamp correctly for included class files (needed for Reproducible
Builds)
-->
<plugin>
<groupId>org.apache.felix</groupId>
<artifactId>maven-bundle-plugin</artifactId>
<executions>
<execution>
<id>bundle-manifest</id>
<phase>process-classes</phase>
<goals>
<goal>manifest</goal>
</goals>
</execution>
</executions>
</plugin>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-jar-plugin</artifactId>
<configuration>
<archive>
<manifestFile>${project.build.outputDirectory}/META-INF/MANIFEST.MF</manifestFile>
</archive>
</configuration>
</plugin>
<!-- 13-May-2025: config defaults for Sonatype Central Portal publishing -->
<plugin>
<groupId>org.sonatype.central</groupId>
<artifactId>central-publishing-maven-plugin</artifactId>
<extensions>true</extensions>
<configuration>
<publishingServerId>central</publishingServerId>
</configuration>
</plugin>
</plugins>
</pluginManagement>
<!-- And one more odd thing... we actually MUST disable checks just for this
pom (but not on something that extends it)
-->
<plugins>
<plugin>
<artifactId>maven-enforcer-plugin</artifactId>
<executions>
<execution>
<id>enforce-properties</id>
<phase>none</phase>
</execution>
</executions>
</plugin>
<!-- 26-May-2025: Enable Sonatype Central Portal publishing -->
<plugin>
<groupId>org.sonatype.central</groupId>
<artifactId>central-publishing-maven-plugin</artifactId>
</plugin>
<!-- 12-Oct-2019, tatu: Copied from
https://github.com/stephenc/git-timestamp-maven-plugin/blob/master/pom.xml#L327-L337
-->
<!-- 11-Jan-2025, tatu: Upgrade 1.6.13 -> 1.7.0 -->
<!-- 26-May-2025, tatu: No longer needed:
<plugin>
<groupId>org.sonatype.plugins</groupId>
<artifactId>nexus-staging-maven-plugin</artifactId>
<version>1.7.0</version>
<extensions>true</extensions>
<configuration>
<serverId>sonatype-nexus-staging</serverId>
<nexusUrl>https://oss.sonatype.org/</nexusUrl>
<stagingProfileId>b34f19b9cc6224</stagingProfileId>
</configuration>
</plugin>
-->
</plugins>
</build>
</project>