discard 16961b3 [MNG-6799] deprecate StringSearchModelInterpolator and remove @Named
discard 24d15c0 [MNG-6789] sisu.inject 3.3.4 produces Reproducible output
discard 5759bc1 [MNG-6789] use packaging plugins' RB versions + plexus-metadata 2.1.0
discard e83c117 inject buildId containing commitId into classifier for CI archive
discard f842628 add sha512 checksum to output
discard 8a916af build on nodes instead of running ITs
add 3a80ae0 [MNG-6799] deprecate StringSearchModelInterpolator and remove @Named
add bd10f00 [MNG-6789] upgrade and configure plugins for Reproducible Builds
new 94f936d build on nodes instead of running ITs
new 841886d add sha512 checksum to output
new 8fe26fa inject buildId containing commitId into classifier for CI archive
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version. This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:
* -- * -- B -- O -- O -- O (16961b3)
N -- N -- N refs/heads/reproducible (8fe26fa)
You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.
Any revisions marked "omit" are not gone; other references still
refer to them. Any revisions marked "discard" are gone forever.
The 3 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.