How jtama/quarkus-extension-demo works
Main Components
a. Extension Core Components:
• Runtime Module
• Deployment Module
• Integration Tests
• Conference Provider
• Configuration Provider
b. Build-time vs Runtime separation (crucial for Quarkus extensions):
• Build-time components (deployment module)
• Runtime components
• Dev Services and Dev UI components
Component Relationships
[Build Time]
Deployment Module
• AcmeConfigurationProviderProcessor
• DevServicesProcessor
• ConfigurationProviderDevUIProcessor
• Build Items Generation
[Runtime]
Runtime Module
• Config Sources
• Environment Provider
• Runtime Configuration
[Development]
Dev UI/Services
• Configuration Provider Card
• JSON RPC Service
[Testing]
Integration Tests
• Custom Resource Tests
Specific Elements
• Blue: Build-time components
• Green: Runtime components
• Orange: Development tools
• Gray: Testing components
b. Component Interactions:
• Build-time to runtime flow
• Configuration source chain
• Extension points
• Dev services integration
Key Architectural Aspects to Highlight
• Configuration Provider Architecture:
• AcmeConfigSource
• ConfigSourceFactory
• Environment Provider integration
• Build Time Processing:
• Processors
• Build Items
• Transformers
• Development Support:
• Dev Services
• Dev UI integration
• Configuration management
Important Details
• Extension points clearly
• Integration with Quarkus core
• Configuration flow
• Build-time vs runtime boundary
• Test coverage scope
Top: Build-time processing
Middle: Runtime components
Bottom: Development and testing tools
Side: External integrations
Remember to:
• Keep the main extension logic flow clear
• Clear separation between build and runtime phases
• Configuration injection points
• Major integration points