quarkusio/quarkus

Allow default exporter with additional Quarkiverse exporters

Open

#36,500 opened on Oct 16, 2023

View on GitHub
 (6 comments) (0 reactions) (0 assignees)Java (2,464 forks)batch import
area/tracinggood first issuekind/enhancement

Repository metrics

Stars
 (12,967 stars)
PR merge metrics
 (Avg merge 6d 4h) (325 merged PRs in 30d)

Description

Description

Currently, when an exporter is present the default exporter in not instantiated. A list of exporters through CDI is possible with Quarkiverse exporters because users can activate and deactivate each one individually, however, we need a new property to activate the default exporter, even if other ones are present. This way we can have many different exporters and the default, working together with CDI.

Contributor guide

Research direction
Implement a new configuration property to enable the default exporter when other Quarkiverse exporters are active. Study the existing exporter instantiation logic and CDI bean discovery.
Tech stack
java
Domain
backend
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
JavaQuarkusCDI
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70