fix: restore developers metadata required by Central Portal

[Chase Poirier (chasepoirier)]

Why

While deploying 3.5.0 to Sonatype Central, validation failed:

Deployment 1d2ac64d-4a7b-405a-a2ae-87d2088e5cc7 failed
pkg:maven/com.contentful.java/cma-sdk@3.5.0:
 - Developers information is missing

Commit 2672ceb ("Release/3.4.23 to master", #207) removed the <developers> block from pom.xml alongside unrelated dependency bumps (okhttp 3.12.1→4.12.0, android.platform 16→21, kotlin-stdlib). Published 3.4.23 still has the block, so it was deployed before that removal landed — this has been latent ever since and blocks every future release.

contentful.java (the CDA SDK) still has its block intact, so only this repo regressed.

What

Restores <developers> in its original position (after <organization>, before <properties>), as a team entry rather than an individual contributor so it doesn't go stale again.

Verification

Re-ran ./mvnw -B clean deploy locally with this change — Central Portal validation passes:

Uploaded bundle successfully, deploymentId: 85a85180-27c2-43ba-9cb7-190c622ddcd9
Deployment 85a85180-27c2-43ba-9cb7-190c622ddcd9 has been validated.

The deployment is validated but not yet published (autoPublish is false), so nothing is live on Central until it's promoted manually.

Summary by Bito

This PR restores the `` metadata block in pom.xml that was accidentally removed during a previous release's dependency updates, which has been blocking Maven Central deployment since version 3.4.23. The fix uses a team-based entry (Contentful Developer Experience) instead of individual contributors to ensure the metadata remains current and prevents future staleness.

Detailed Changes

• Restores `` section in pom.xml (lines 37-45) with team-based entry to resolve Sonatype Central Portal validation error that was blocking Maven Central deployment
• Replaces individual contributor entry with team identity (id: contentful-dx, email: prd-ecosystem-dx@contentful.com) to prevent staleness on personnel changes
• Positions developers block after `` and before `` following Maven POM conventions

[bito-code-review]

Code Review Agent Run #88774a

Actionable Suggestions - 0

Review Details

• Files reviewed - 1 · Commit Range: 34bc29b..34bc29b

  • pom.xml
• Files skipped - 0
• Tools

  • Whispers (Secret Scanner) - ✔︎ Successful
  • Detect-secrets (Secret Scanner) - ✔︎ Successful

---

Bito Usage Guide

Commands

Type the following command in the pull request comment and save the comment.

• /review - Manually triggers a full AI review.

• /pause - Pauses automatic reviews on this pull request.

• /resume - Resumes automatic reviews.

• /resolve - Marks all Bito-posted review comments as resolved.

• /abort - Cancels all in-progress reviews.

Refer to the documentation for additional commands.

Configuration

This repository uses Default Agent You can customize the agent settings here or contact your Bito workspace admin at jared.jolton@contentful.com.

Documentation & Help

• Customize agent settings
• Review rules
• General documentation
• FAQ

AI Code Review powered by

[bito-code-review]

Changelist by Bito

This pull request implements the following key changes.

Key Change	Files Impacted	Summary
Bug Fix - Maven Central deployment metadata fix	pom.xml	Restores the section in pom.xml required by Sonatype Central Portal for Maven Central deployment validation.

[bito-code-review]

Impact Analysis by Bito

Interaction Diagram

sequenceDiagram
participant Build as Maven Build System<br/>🔄 Updated | ●○○ Low
participant POM as pom.xml<br/>🟩 Added | ●○○ Low
participant Dev as Contentful Developer Experience<br/>🟩 Added | ●○○ Low
participant Config as Maven Configuration<br/>🔄 Updated | ●○○ Low
Note over POM: Metadata update - adding developer entry<br/>for Contentful Developer Experience team
Build->>POM: Validate project configuration
POM->>Config: Load project properties
Config->>Dev: Register developer metadata
Dev-->>Config: Developer info configured
Config-->>POM: Configuration complete

Loading

---

This PR adds a developer metadata entry to the Maven pom.xml file, identifying the Contentful Developer Experience team as a project contributor. This is a pure configuration change with no impact on Java source code, compilation, or runtime behavior. No upstream or downstream dependencies or cross-repo impacts are affected by this metadata update.

Code Paths Analyzed

Impact:
Minimal. This PR only adds developer metadata to pom.xml. No code, APIs, or dependencies are modified.

Flow:
N/A - No code paths affected. This is purely a Maven POM metadata change.

Direct Changes (Diff Files):
• pom.xml [9-17] — Added <developers> section with Contentful Developer Experience team information (id, name, email, organization, organizationUrl)

Repository Impact:
• None.

Cross-Repository Dependencies:
• None.

Database/Caching Impact:
• None

API Contract Violations:
• None.

Infrastructure Dependencies:
• None.

Additional Insights:
• Maven artifact metadata: The added developer metadata will appear in generated Maven artifacts (JARs, documentation). This is informational only and does not affect runtime behavior.

Testing Recommendations

Frontend Impact:
• None.

Service Integration:
• None.

Data Serialization:
• None.

Privacy Compliance:
• None.

Backward Compatibility:
• No compatibility concerns. This is a metadata-only change that does not affect the artifact's API, functionality, or dependencies.

OAuth Functionality:
• None

Reliability Testing:
• None

Additional Insights:
• Standard Maven build verification (mvn compile, mvn package) will confirm the POM is valid and the metadata is correctly embedded.

_{Analysis based on known dependency patterns and edges. Actual impact may vary.}

[bito-code-review]

✅ Review Settings Overridden

Status: Overridden Successfully

Guidelines:

• Accepted:

  • General : Review Posture, Repo Truth And Alignment, Domain Invariants

Note: Extra guidelines beyond 3 general purpose guidelines and 1 language specific guideline per language are not processed. Guidelines are fetched from the source branch.