CAMEL-24318 - Use Maven parallelization for deploy on Jenkins

[apupier]

• locally with local repo (take care to deactivate local build cache):
  • 8'32" ( ./mvnw -T1C -U -B -e -fae -V -Dnoassembly -Pdeploy,apache-snapshots -Dquickly clean deploy
    -DaltDeploymentRepository=your_repo_id::default::file:/tmp/alt-repo-2 )
  • 18'33" (./mvnw -U -B -e -fae -V -Dnoassembly
    -Pdeploy,apache-snapshots -Dquickly clean deploy
    -DaltDeploymentRepository=your_repo_id::default::file:/tmp/alt-repo-2)
• on jenkins for Camel core:
  • 25min instead of usually 3 hours, previous record was 2h35 , see https://ci-builds.apache.org/job/Camel/job/Camel%20Daily%20Snapshot%20Deploy/job/main/1494/

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.

[gnodet]

Claude Code on behalf of Guillaume Nodet

Adding -T1C to the snapshot deploy pipeline is a well-tested, low-risk optimization. The deploy pipeline uses -Dquickly (skipping tests/formatting/enforcement), and all plugins involved (compiler, deploy, source, javadoc) are thread-safe. The PR provides good performance evidence — local measurements (8m32s vs 18m33s) and a Jenkins build link (build #1494 at 25min vs the typical ~3h baseline).

Key observations:

• The main Jenkinsfile (full build with tests) is correctly left unchanged — full builds with test execution carry higher thread-safety risk
• The existing -fae (fail-at-end) flag is the correct companion for -T1C
• Maven reactor properly respects inter-module dependency ordering even with -T1C
• Memory consumption may increase with parallel builds since multiple modules compile and generate javadoc simultaneously — worth monitoring after merge, though the Jenkins test (build #1494) demonstrates sufficient resources