Skip to content

Annotation Removal ​

Current posture: YAML authority is rising, but annotations remain part of extraction.

AnnotationCurrent rolePortability stance
@PipelineStepBuild-time marker and metadata sourceMake optional; migrate metadata to YAML or neutral descriptors
@PipelineOrchestratorOrchestrator endpoint and generation triggerReplace with YAML orchestrator declaration
@PipelinePluginPlugin host markerReplace with service descriptor metadata
@GeneratedRoleInternal generated markerKeep internally
@ParallelismHintRuntime/compiler hintKeep as neutral internal metadata or descriptor fields

Suggested migration path:

  1. Keep annotations supported.
  2. Make YAML service declarations authoritative.
  3. Validate service signatures directly from YAML class names.
  4. Warn on annotation/YAML conflicts.
  5. Move operational metadata (cache keys, ordering, virtual thread hints, side-effects) to YAML.
  6. End with annotations optional, then remove Quarkus-only public annotation coupling.