Reduce SpringQuartzPersistentStoreRestartAppChangeOptionsTest.testRes…

[apupier]

…tartAppChangeTriggerOptions

flakiness

in case of one first flaky failure, the next 2 runs were failing due to conflicting JMX ObjectName MBean because the application was not correctly closed

org.apache.camel.RuntimeCamelException:
org.apache.camel.VetoCamelContextStartException: CamelContext
(camelContext-SpringQuartzPersistentStoreRestartAppChangeOptionsTest)
with ObjectName[org.apache.camel:context=camelContext-SpringQuartzPersistentStoreRestartAppChangeOptionsTest,type=context,name="camelContext-SpringQuartzPersistentStoreRestartAppChangeOptionsTest"]
is already registered. Make sure to use unique names on CamelContext
when using multiple CamelContexts in the same MBeanServer.

see https://develocity.apache.org/s/5x3nw5526ik7m/tests/goal/org.apache.camel:camel-quartz:surefire:test@default-test/details/org.apache.camel.component.quartz.SpringQuartzPersistentStoreRestartAppChangeOptionsTest/testRestartAppChangeTriggerOptions?top-execution=1

Description

Target

• I checked that the commit is targeting the correct branch (Camel 4 uses the main branch)

Tracking

• If this is a large change, bug fix, or code improvement, I checked there is a JIRA issue filed for the change (usually before you start working on it).

Apache Camel coding standards and style

• I checked that each commit in the pull request has a meaningful subject line and body.

• I have run mvn clean install -DskipTests locally from root folder and I have committed all auto-generated changes.

AI-assisted contributions

• If this PR includes AI-generated code, commits have proper co-authorship attribution (e.g., Co-authored-by trailers) and the PR description identifies the AI tool used.

[github-actions]

🌟 Thank you for your contribution to the Apache Camel project! 🌟
🤖 CI automation will test this PR automatically.

🐫 Apache Camel Committers, please review the following items:

• First-time contributors require MANUAL approval for the GitHub Actions to run
• You can use the command /component-test (camel-)component-name1 (camel-)component-name2.. to request a test from the test bot although they are normally detected and executed by CI.
• You can label PRs using skip-tests and test-dependents to fine-tune the checks executed by this PR.
• Build and test logs are available in the summary page. Only Apache Camel committers have access to the summary.

⚠️ Be careful when sharing logs. Review their contents before sharing them publicly.

[github-actions]

🧪 CI tested the following changed modules:

• components/camel-quartz

---

🔬 Scalpel shadow comparison — Scalpel: 1 tested, 0 compile-only — current: 12 all tested

Maveniverse Scalpel detected 1 affected modules (current approach: 12).

Modules only in current approach (11)

• camel-jbang-mcp
• camel-jbang-plugin-mcp
• camel-jbang-plugin-route-parser
• camel-jbang-plugin-tui
• camel-jbang-plugin-validate
• camel-launcher-container
• camel-mail
• camel-mail-microsoft-oauth
• camel-yaml-dsl-validator
• camel-yaml-dsl-validator-maven-plugin
• camel-zookeeper-master

Skip-tests mode would test 1 modules (1 direct + 0 downstream), skip tests for 0 (generated code, meta-modules)

Modules Scalpel would test (1)

• camel-quartz

ℹ️ Shadow mode — Scalpel observes but does not affect test execution. Learn more

All tested modules (12 modules)

• Camel :: JBang :: MCP
• Camel :: JBang :: Plugin :: MCP
• Camel :: JBang :: Plugin :: Route Parser
• Camel :: JBang :: Plugin :: TUI
• Camel :: JBang :: Plugin :: Validate
• Camel :: Launcher :: Container
• Camel :: Mail
• Camel :: Mail :: Microsoft OAuth
• Camel :: Quartz
• Camel :: YAML DSL :: Validator
• Camel :: YAML DSL :: Validator Maven Plugin
• Camel :: Zookeeper Master

---

⚙️ View full build and test results