When user use the bom file, they don't need to specify the version of camel-xxx component. If we remove the dependency management section form BOM, the old pom.xml may not work any more. They need to specify the camel version for the camel-xxx component in their pom.
We need to inform the end user in the migration document, if we merged the PR. Willem Jiang Twitter: willemjiang Weibo: 姜宁willem On Mon, Jul 1, 2019 at 8:10 PM Guillaume Nodet <[email protected]> wrote: > > I've been spending quite some time last week to try to improve the time > spent by maven before actually starting building something. > I've opened a few PR on maven which should reduce by 50% the time, but I > noticed that a lot of time is spent because the camel parent pom has 800 > dependencies in the dependency management section. > So I was wondering if we should remove the camel modules from the > dependency management section. I experimented that, so this is available > at > https://github.com/apache/camel/pull/3009 > With the above , the execution of `mvn foo` (which fails fast) goes from 54 > seconds to 39 seconds. With the addition maven PRs, it goes down to 28 > seconds. > Thoughts ? > > -- > ------------------------ > Guillaume Nodet
