[camel-k-runtime] branch 953/update-dsl-metadata updated (90ce144e -> 7b0d4e6d)

[nf...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

nfilotto pushed a change to branch 953/update-dsl-metadata
in repository https://gitbox.apache.org/repos/asf/camel-k-runtime.git


    omit 90ce144e Ref #953: Update DSLs metadata
     add 92c4187c build(deps): bump maven-pmd-plugin from 3.19.0 to 3.20.0
     add 24587ac7 Updated CHANGELOG.md
     add 343042b3 build(deps): bump jolokia-jvm from 1.7.1 to 1.7.2
     add f1c3df45 build(deps): bump groovy-version from 3.0.13 to 3.0.14
     add 394c4973 build(deps): bump maven-failsafe-plugin from 3.0.0-M7 to 3.0.0-M8
     add 7d880b1b Updated CHANGELOG.md
     add f5a15cac Move jolokia exclusions from generate-catalog maven plugin to the camel-k-runtime-bom/pom.xml
     add dafe23b4 Updated CHANGELOG.md
     add 7b0d4e6d Ref #953: Update DSLs metadata

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   (90ce144e)
            \
             N -- N -- N   refs/heads/953/update-dsl-metadata (7b0d4e6d)

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.

No new revisions were added by this update.

Summary of changes:
 CHANGELOG.md                                       |  9 +++++++++
 pom.xml                                            |  6 +++---
 .../camel/k/tooling/maven/GenerateCatalogMojo.java | 22 ++++++++--------------
 support/camel-k-runtime-bom/pom.xml                | 12 +++++++++++-
 4 files changed, 31 insertions(+), 18 deletions(-)