Add an automatic module name to the MANIFEST

[LonelyMidoriya]

Summary by CodeRabbit

• Chores
  • Updated parent project dependency version to latest stable release.
  • Enhanced JAR manifest configuration to support Java module system compatibility, improving interoperability in modular Java environments.

[coderabbitai]

Walkthrough

The pull request updates the parent POM version from 1.29.1 to 1.29.6 and configures the maven-jar-plugin to include an Automatic-Module-Name entry in the JAR manifest, enabling Java 9+ module system support.

Changes

Cohort / File(s)	Summary
POM Configuration pom.xml	Parent version bumped to 1.29.6; maven-jar-plugin added to set Automatic-Module-Name to org.verapdf.pdf.model in JAR manifest

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

• Straightforward version bump with no dependency chain concerns
• Standard maven-jar-plugin configuration pattern for module naming

Poem

🐰 A version hops forward, 1.29.6 comes to stay,
And modules get names, the Java 9+ way!
The manifest whispers "org.verapdf.pdf.model" bright,
Configuration complete—our JAR takes flight! 📦✨

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'Add an automatic module name to the MANIFEST' directly and clearly describes the main change—adding an Automatic-Module-Name entry to the JAR manifest via maven-jar-plugin configuration.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch automatic-module-name

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between fd1ec7f and 0cc46b4.

📒 Files selected for processing (1)

• pom.xml (2 hunks)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)

• GitHub Check: Codacy Static Code Analysis

🔇 Additional comments (2)

pom.xml (2)

78-88: Module name follows Java module system conventions.

The Automatic-Module-Name "org.verapdf.pdf.model" appropriately derives from the project's group ID (org.verapdf) and artifact ID (pdf-model), following standard Java module naming conventions. This configuration correctly enables Java 9+ module system support without breaking backward compatibility.

---

78-88: Cannot verify Automatic-Module-Name alignment—repository contains no Java source code.

The repository contains only model definition files (.mdl format) under src/main/java/ with no actual Java source files or package declarations. The Automatic-Module-Name configuration in pom.xml cannot be verified against package structure because there are no Java packages present. Either the repository state is incomplete or source code is generated/compiled elsewhere. Clarify the project structure before this configuration can be meaningfully validated.

[coderabbitai]

⚠️ Potential issue | 🔴 Critical

🧩 Analysis chain

Verify parent POM version 1.29.6 for compatibility.

The parent version is being bumped from 1.29.1 to 1.29.6. Confirm this version exists and review the changelog to ensure there are no breaking changes or dependency conflicts.

---

🏁 Script executed:

#!/bin/bash
# Description: Verify parent POM version 1.29.6 exists and retrieve details.

# Search for the parent POM in Maven Central and check if version exists
curl -s "https://repo.maven.apache.org/maven2/org/verapdf/verapdf-parent/1.29.6/verapdf-parent-1.29.6.pom" -o /dev/null -w "HTTP Status: %{http_code}\n"

Length of output: 16

---

---

🏁 Script executed:

```shell
#!/bin/bash
# Description: Check available versions of verapdf-parent in Maven Central

# List available versions by querying Maven Central metadata
curl -s "https://repo.maven.apache.org/maven2/org/verapdf/verapdf-parent/maven-metadata.xml" | grep -oP '(?<=<version>)[^<]+'

Length of output: 128

---

Critical: Parent POM version 1.29.6 does not exist in Maven Central Repository.

The parent version specified (1.29.6) is unavailable in Maven Central. Available versions of verapdf-parent only extend to 1.28.2. The build will fail unless this is resolved. Either:

• Verify the version number is correct for your repository configuration
• Use an available version (latest is 1.28.2)
• Confirm a custom/private repository contains 1.29.6

🤖 Prompt for AI Agents

In pom.xml around line 30, the parent POM version is set to 1.29.6 which does
not exist in Maven Central; update the parent version to an available release
(for example 1.28.2) or change/add your repository configuration that hosts
1.29.6. Edit the <version> value to a published version or add the
custom/private repository entry where 1.29.6 is hosted and re-run mvn validate
to ensure Maven can resolve the parent POM.