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

zregvart pushed a change to branch website
in repository https://gitbox.apache.org/repos/asf/camel.git.


 discard bdf3a1b  CAMEL-11492 New Camel website - version upgrades
 discard fe66694  CAMEL-11492 New Camel website - added README.md
 discard fc695fc  CAMEL-11492 New Camel website
 discard 5130bb38 CAMEL-11492 New Camel website
     add c9b7719  Remove mchange-commons-java property placeholder as it's not 
used
     add a3c1a23  Upgrade Jose4j to version 0.6.4
     new cb4a934  CAMEL-11492 New Camel website
     new 23839da  CAMEL-11492 New Camel website
     new 7222af6  CAMEL-11492 New Camel website - added README.md
     new bc3594d  CAMEL-11492 New Camel website - version upgrades
     new cd3f00f  Update website to 2.23.0-SNAPSHOT
     new 058ed0d  Test website Jenkinsfile

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   (bdf3a1b)
            \
             N -- N -- N   refs/heads/website (058ed0d)

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 6 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.


Summary of changes:
 Jenkinsfile                | 71 ++++++++++++++++++++++++++++++++++++++++++++++
 camel-website/package.json |  2 +-
 camel-website/pom.xml      |  2 +-
 parent/pom.xml             |  3 +-
 4 files changed, 74 insertions(+), 4 deletions(-)

Reply via email to