Skip to content

Commit 114f719

Browse files
committed
Merge branch '3.2' into 3.x
2 parents 018267d + 34fbd96 commit 114f719

1 file changed

Lines changed: 37 additions & 0 deletions

File tree

pom.xml

Lines changed: 37 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -410,4 +410,41 @@ tools.jackson.core.*;version=${project.version}
410410
<scope>test</scope>
411411
</dependency>
412412
</dependencies>
413+
414+
<profiles>
415+
<!-- 26-Jun-2026, tatu: [core#1625] (regression of [core#1561]) Javadoc generation
416+
is broken when built with JDK 17 (the produced `-javadoc.jar` is missing the
417+
index/search/overview files, so javadoc.io cannot render it). JDK 21+ is needed
418+
to produce a complete Javadoc jar. Releases run via `release:perform` with
419+
`-Prelease` (see maven-release-plugin config in parent), and the `release`
420+
profile is where the Javadoc jar gets attached, so guard exactly that build
421+
and fail fast if it is not run on JDK 21 or higher. Normal development on JDK 17
422+
is unaffected.
423+
-->
424+
<profile>
425+
<id>release</id>
426+
<build>
427+
<plugins>
428+
<plugin>
429+
<artifactId>maven-enforcer-plugin</artifactId>
430+
<executions>
431+
<execution>
432+
<id>enforce-jdk21-for-release</id>
433+
<phase>validate</phase>
434+
<goals><goal>enforce</goal></goals>
435+
<configuration>
436+
<rules>
437+
<requireJavaVersion>
438+
<version>[21,)</version>
439+
<message>[ERROR] Releases must be built with JDK 21 or higher so that the Javadoc jar is complete (see jackson-core#1561 / #1625).</message>
440+
</requireJavaVersion>
441+
</rules>
442+
</configuration>
443+
</execution>
444+
</executions>
445+
</plugin>
446+
</plugins>
447+
</build>
448+
</profile>
449+
</profiles>
413450
</project>

0 commit comments

Comments
 (0)