[
https://issues.apache.org/jira/browse/CAMEL-17894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Otavio Rodolfo Piske resolved CAMEL-17894.
------------------------------------------
Resolution: Fixed
Resolved by CAMEL-19465, CAMEL-19461 and CAMEL-19466. Via PR:
https://github.com/apache/camel/pull/10476
> build: investigate ways to make it faster
> -----------------------------------------
>
> Key: CAMEL-17894
> URL: https://issues.apache.org/jira/browse/CAMEL-17894
> Project: Camel
> Issue Type: Task
> Components: build system
> Reporter: Otavio Rodolfo Piske
> Assignee: Otavio Rodolfo Piske
> Priority: Major
> Fix For: 3.x, 4.0.0
>
> Attachments: build-stats.txt, camel-build-times.txt, mvn-profile.html
>
>
> [This
> talk|https://peter.palaga.org/presentations/220328-maven-jug-luzern-and-zurich/index.html]
> from from [~ppalaga] has some interesting ideas we can use to improve our
> build time.
> 1. Investigate whether we can tweak our default build profile to fully skip
> certain plugin executions, so that we avoid potentially costly operations
> pre-execution (related to instantiating them).
> For instance, we can evaluate disabling validation, formatting and other
> plugins in the default execution and only enable them on the sourcecheck
> profile
> 2. Use the Async profiler to find and fix bottlenecks in our own Maven
> plugins, to reduce their execution time and load.
>
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
