[WIP] Feature: CRD Generation to POJO Classes at Maven Build Time

[maeveho25]

This PR adds a new feature that automatically generates Java POJO classes from Tekton Custom Resource Definitions (CRDs) during Maven build time.

What's Added

Core Components

• CrdJavaGenerator Main entry point for Maven exec plugin integration.

• EnhancedCrdProcessor Core logic for processing CRD YAML files and generating Java classes using jsonschema2pojo.

• Maven Profile Integration A new Maven profile download-binaries is added for:

  • CRD generation
  • JX Pipeline binary downloads

Generated Output

• 1000+ Java Classes generated from Tekton CRD schemas
• Support for Multiple API Versions: v1, v1beta1, v1alpha1
• Jenkins Integration: All generated classes extend BaseStep and include @DataBoundConstructor for pipeline compatibility

Next Steps

• CRD to POJO generation logic
• UI Integration
  • Auto-generate Jelly files for Jenkins UI rendering
• Unit Tests
  • Validate POJO generation from mock CRD YAML
  • Test CRD processor with various CRD formats and edge cases
• Generated POJO Tests
  • Test core methods such as createCustomTaskRun, pipeline, etc.
  • Verify all generated steps extend BaseStep
• End-to-End Testing
  • CRD → POJO → Jenkins Step → Kubernetes API

Submitter checklist

• Make sure you are opening from a topic/feature/bugfix branch (right side) and not your main branch!
• Ensure that the pull request title represents the desired changelog entry
• Please describe what you did
• Link to relevant issues in GitHub or Jira
• Link to relevant pull requests, esp. upstream and downstream changes
• Ensure you have provided tests that demonstrate the feature works or the issue is fixed

Architecture Diagram

CRD YAML Files
       ↓
CrdJavaGenerator
       ↓
EnhancedCrdProcessor
       ↓
jsonschema2pojo
       ↓
Generated POJOs

[maeveho25]

Fix: Disable equals/hashCode generation to avoid SpotBugs issues

Root cause: jsonschema2pojo library generates equals() methods with problematic string comparison (== instead of .equals()), causing SpotBugs violations.

Solution: Disable equals/hashCode generation entirely by setting isIncludeHashcodeAndEquals() = false.

Explanation on this approach:

• Generated POJOs are used as DTOs for JSON serialization/Jenkins binding only
• They don't need object comparison in business logic
• Cleaner than post-processing or forking the library to fix the template

[Copilot]

Pull Request Overview

This PR introduces a comprehensive CRD (Custom Resource Definition) to POJO generation feature for the Tekton Jenkins plugin, automatically generating over 1000 Java classes from Tekton CRD schemas during Maven build time. The feature enables automatic creation of typed Java classes that extend BaseStep for Jenkins pipeline integration.

Key changes include:

• Core CRD processing engine using jsonschema2pojo with enhanced inheritance capabilities
• Maven integration for automatic POJO generation during build time
• Addition of multiple Tekton CRD YAML files (pipeline, task, stepaction, etc.)

Reviewed Changes

Copilot reviewed 13 out of 17 changed files in this pull request and generated 2 comments.

Show a summary per file

File	Description
src/main/java/org/waveywaves/jenkins/plugins/tekton/generator/EnhancedCrdProcessor.java	Core CRD processing logic that converts YAML schemas to Java POJOs with Jenkins BaseStep inheritance
src/main/java/org/waveywaves/jenkins/plugins/tekton/generator/CrdJavaGenerator.java	Maven exec plugin entry point for CRD generation with Jenkins-specific configuration
src/main/resources/crds/*.yaml	Multiple Tekton CRD definition files for pipeline, task, stepaction, and other resources
pom.xml	Maven configuration updates including new dependencies, exec plugin setup, and build process changes
src/test/java/org/waveywaves/jenkins/plugins/tekton/client/build/delete/DeleteRawTest.java	Test import addition for DeleteAllBlock inner class

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[maeveho25]

hi @krisstern I have fixed the security warning

[maeveho25]

Fix: Disable equals/hashCode generation to avoid SpotBugs issues

Root cause: jsonschema2pojo library generates equals() methods with problematic string comparison (== instead of .equals()), causing SpotBugs violations.

Solution: Disable equals/hashCode generation entirely by setting isIncludeHashcodeAndEquals() = false.

Explanation on this approach:

• Generated POJOs are used as DTOs for JSON serialization/Jenkins binding only
• They don't need object comparison in business logic
• Cleaner than post-processing or forking the library to fix the template

@waveywaves this is the issue i was talking about

[jonesbusy]

Just an open question here (Maybe this discussion already happend).

Any reason to not use https://github.com/fabric8io/kubernetes-client/blob/main/doc/java-generation-from-CRD.md to generate the Java Object from CRDs?

This can be used with java-generator-maven-plugin maven plugin and specifying the location of the CRDs

Since we already have the https://plugins.jenkins.io/kubernetes-client-api/ it should not be an issue to have such POJO implement interface like (HasMetadata)

I used the mentionned approach not so long ago to generate Java classes from Flux CD CRDs (like HelmRelease) and this works like a charm (fabric8io/kubernetes-client#7130)

Looking at the config and dependencies added this look fragile to me, but maybe I miss the reason

[maeveho25]

Just an open question here (Maybe this discussion already happend).

Any reason to not use https://github.com/fabric8io/kubernetes-client/blob/main/doc/java-generation-from-CRD.md to generate the Java Object from CRDs?

This can be used with java-generator-maven-plugin maven plugin and specifying the location of the CRDs

Since we already have the https://plugins.jenkins.io/kubernetes-client-api/ it should not be an issue to have such POJO implement interface like (HasMetadata)

I used the mentionned approach not so long ago to generate Java classes from Flux CD CRDs (like HelmRelease) and this works like a charm (fabric8io/kubernetes-client#7130)

Looking at the config and dependencies added this look fragile to me, but maybe I miss the reason

Thank you for pointing that out! Your approach definitely looks more efficient. I’m looking into it now and will work on applying it.