Peter Palaga created CAMEL-19465:
------------------------------------
Summary: Move Apache snapshots repository to a separate Maven
profile for better build reproducibility
Key: CAMEL-19465
URL: https://issues.apache.org/jira/browse/CAMEL-19465
Project: Camel
Issue Type: Improvement
Reporter: Peter Palaga
Remote Maven snapshots are handy for third parties to quickly integrate with
the newest changes in Camel. However, they should not be enabled as a part of
the default build of Camel itself. Enabling them may cause or hide several
kinds of issues:
* There is no guarantee that the state of the snapshot repository is
consistent: at any point in time it can contain artifacts from one or more
builds that were based on one or more source commits. Combining artifacts built
from multiple builds can lead to all kinds of incompatibilities or the other
way round, it can happily hide an incompatibility introduced recently.
* The snapshots are deployed with some delay against the state of the main
branch. A new module merged to main now will be available only after few hours
in the snapshots repo. This will inevitably make all PR CI jobs that rely on
snapshots fail in that period.
* Snapshots are simply "the latest": latest today is not the same as latest
tomorrow. That breaks the reproducibility of the builds.
Hence I am hereby proposing to move Apache snapshots repository to a separate
Maven profile so that folks wanting to use it can continue to do so, but the
default build will become more reliable and reproducible.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
