This is an automated email from the ASF dual-hosted git repository.
davsclaus pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/camel-website.git
The following commit(s) were added to refs/heads/main by this push:
new 6d80eb58 Remove EOL docs for Camel K 1.12.x and its associated EOL sub
projects. (#1147)
6d80eb58 is described below
commit 6d80eb580e52becc486d5c4c35f432a7eeedf92d
Author: Claus Ibsen <[email protected]>
AuthorDate: Tue Feb 20 12:23:10 2024 +0100
Remove EOL docs for Camel K 1.12.x and its associated EOL sub projects.
(#1147)
* Remove EOL docs for Camel K 1.12.x and its associated EOL sub projects.
* Remove EOL docs for Camel K 1.12.x and its associated EOL sub projects.
* Remove links from old blogs for EOL releases
---
antora-playbook-snippets/antora-playbook.yml | 9 ---------
content/blog/2020/06/camel-k-release-1.0.0/index.md | 2 +-
content/blog/2020/12/Camel37-Whatsnew/index.md | 15 +++++++--------
content/blog/2022/07/camel-k-monitoring-ops/index.md | 2 +-
content/blog/2023/02/camel-k-release-1-12/index.md | 2 +-
content/blog/2023/03/camel-k-telemetry/index.md | 4 ++--
content/blog/2023/04/camel-observation/index.md | 2 +-
content/blog/2023/05/camel-debezium-quarkus/index.md | 10 +++++-----
8 files changed, 18 insertions(+), 28 deletions(-)
diff --git a/antora-playbook-snippets/antora-playbook.yml
b/antora-playbook-snippets/antora-playbook.yml
index 5900b408..3434a3f9 100644
--- a/antora-playbook-snippets/antora-playbook.yml
+++ b/antora-playbook-snippets/antora-playbook.yml
@@ -21,7 +21,6 @@ content:
- camel-4.0.x
- camel-3.22.x
- camel-3.21.x
- - camel-3.20.x
start_paths:
# eip
- core/camel-core-engine/src/main/docs
@@ -34,23 +33,18 @@ content:
branches:
- main
- release-2.2.x
- - release-1.12.x
start_path: docs
- # We may remove this module as soon as Camel K 2.1 (release-2.1.x) is no
longer supported.
- url: https://github.com/apache/camel-k-runtime.git
branches:
- main
- release-3.2.x
- - release-1.17.x
start_path: docs
- url: https://github.com/apache/camel-kamelets.git
branches:
- main
- 4.0.x
- - 3.21.x
- - 3.20.x
start_path: docs
- url: https://github.com/apache/camel-quarkus.git
@@ -58,7 +52,6 @@ content:
- main
- 3.7.x
- 3.2.x
- - 2.16.x
start_path: docs
- url: https://github.com/apache/camel-quarkus-examples.git
@@ -80,7 +73,6 @@ content:
- camel-spring-boot-4.0.x
- camel-spring-boot-3.22.x
- camel-spring-boot-3.21.x
- - camel-spring-boot-3.20.x
start_paths:
- components-starter
- core
@@ -92,7 +84,6 @@ content:
- main
- camel-karaf-3.22.x
- camel-karaf-3.21.x
- - camel-karaf-3.20.x
start_path: docs
ui:
diff --git a/content/blog/2020/06/camel-k-release-1.0.0/index.md
b/content/blog/2020/06/camel-k-release-1.0.0/index.md
index d0f1ef4e..39926006 100644
--- a/content/blog/2020/06/camel-k-release-1.0.0/index.md
+++ b/content/blog/2020/06/camel-k-release-1.0.0/index.md
@@ -202,7 +202,7 @@ Now, let's suppose you want to see what your routes are
doing and trace the exec
kamel run Routes.java -t prometheus.enabled=true -t tracing.enabled=true
```
-That's it again. The Camel K operator will add the [camel-opentracing
library](/components/3.20.x/others/opentracing.html) and **connect it to the
Jaeger collector that is available in the namespace**.
+That's it again. The Camel K operator will add the camel-opentracing library
and **connect it to the Jaeger collector that is available in the namespace**.
Here again, [advanced use cases](/camel-k/next/traits/tracing.html) are
supported.
## Master routes
diff --git a/content/blog/2020/12/Camel37-Whatsnew/index.md
b/content/blog/2020/12/Camel37-Whatsnew/index.md
index 2f60ecf8..ccd270a0 100644
--- a/content/blog/2020/12/Camel37-Whatsnew/index.md
+++ b/content/blog/2020/12/Camel37-Whatsnew/index.md
@@ -20,7 +20,7 @@ This release introduces a set of new features and noticeable
improvements that w
We continued our avenue of making Camel faster and smaller. This time we
focused on the built-in Simple scripting
language.
-First we added the [jOOR
language](/components/3.20.x/languages/joor-language.html). jOOR is a small
Java tool for
+First we added the [jOOR
language](/components/next/languages/joor-language.html). jOOR is a small Java
tool for
performing runtime compilation of Java source code in-memory. It has some
limitations but generally works well for small
scripting code (requires Java 11 onwards).
@@ -28,7 +28,7 @@ Then we worked on compiled simple.
### Compiled Simple
-The [csimple language](/components/3.20.x/languages/csimple-language.html)
+The [csimple language](/components/next/languages/csimple-language.html)
is parsed into regular Java source code and compiled together with all the
other source code, or compiled once during
bootstrap via jOOR.
@@ -123,7 +123,7 @@ microservice/serverless architectures, with a _closed
world_ assumption.
### Autowiring components
The Camel components is now capable of autowiring by type. For example
-the [AWS2 SQS](/components/3.20.x/aws2-sqs-component.html) components can
automatically lookup in the registry if there is
+the [AWS2 SQS](/components/next/aws2-sqs-component.html) components can
automatically lookup in the registry if there is
a single instance of `SqsClient`, and then pre configure itself.
We have marked up in the Camel documentation which component options supports
this by showing *Autowired* in bold in the
@@ -132,19 +132,19 @@ description.
### Salesforce fixes
Our recent Camel committer [Jeremy Ross](https://github.com/jeremyross) did
great work to improve and fix bugs in
-the [camel-salesforce
component](/components/3.20.x/salesforce-component.html). We expect more to
come from him.
+the [camel-salesforce component](/components/next/salesforce-component.html).
We expect more to come from him.
### VertX Kafka Component
A new Kafka component has been developed that uses the Vert.X Kafka Java
Client which allows us to use all of its
features, and also its robustness and stability.
-The [camel-vertx-kafka](/components/3.20.x/vertx-kafka-component.html)
component is intended to be (more) feature
+The camel-vertx-kafka component is intended to be (more) feature
complete with the existing camel-kafka component. We will continue this work
for the next couple of Camel releases.
### DataSonnet
-The new
[camel-datasonnet](/components/3.20.x/languages/datasonnet-language.html)
component, is to be used for data
+The new
[camel-datasonnet](/components/next/languages/datasonnet-language.html)
component, is to be used for data
transformation using the [DataSonnet](https://datasonnet.com/) standard.
DataSonnet is an open source JSON-centric, template-based data transformation
standard built to rival proprietary
@@ -158,8 +158,7 @@ We have upgraded to Spring Boot 2.4.
This release has a number of new components, data formats and languages:
-- [AtlasMap](/components/3.20.x/atlasmap-component.html): Transforms the
message using
- an [AtlasMap](https://www.atlasmap.io/) transformation
+- AtlasMap: Transforms the message using an
[AtlasMap](https://www.atlasmap.io/) transformation
- Kubernetes Custom Resources: Perform operations on Kubernetes Custom
Resources and get notified on Deployment changes
- Vert.X Kafka: Sent and receive messages to/from an Apache Kafka broker using
vert.x Kafka client
- JSON JSON-B: Marshal POJOs to JSON and back using JSON-B
diff --git a/content/blog/2022/07/camel-k-monitoring-ops/index.md
b/content/blog/2022/07/camel-k-monitoring-ops/index.md
index d493e6c0..848f6586 100644
--- a/content/blog/2022/07/camel-k-monitoring-ops/index.md
+++ b/content/blog/2022/07/camel-k-monitoring-ops/index.md
@@ -10,7 +10,7 @@ Camel K offers a wide list of operations you can execute once
your Integration h
## MicroProfile metrics component
-First of all let's start presenting the Apache Camel component that will make
the most of the heavy lift work for you: [Camel Microprofile
Metrics](/components/3.20.x/microprofile-metrics-component.html). This
components is in charge to automatically expose a series of default basic
metrics for every Camel route. Moreover, with this component you can include
your own metrics (please, refer to the documentation to see how to do that).
The standard set of metrics is quite extensive already [...]
+First of all let's start presenting the Apache Camel component that will make
the most of the heavy lift work for you: Camel Microprofile Metrics. This
components is in charge to automatically expose a series of default basic
metrics for every Camel route. Moreover, with this component you can include
your own metrics (please, refer to the documentation to see how to do that).
The standard set of metrics is quite extensive already and can be used to
provide a wide variety of information [...]
When the component is available, the Integration will expose a _/q/metrics_
endpoint and you can use it for monitoring purposes.
diff --git a/content/blog/2023/02/camel-k-release-1-12/index.md
b/content/blog/2023/02/camel-k-release-1-12/index.md
index 16c890ba..59daa5b4 100644
--- a/content/blog/2023/02/camel-k-release-1-12/index.md
+++ b/content/blog/2023/02/camel-k-release-1-12/index.md
@@ -55,7 +55,7 @@ We're now looking forward to see a ton of new tools based on
Camel K!
## Distributed Tracing support moving to OpenTelemetry
-If you are already using Distributed Tracing tools then you might already know
that the [CNCF](https://www.cncf.io) announced that they were [archiving the
OpenTracing
project](https://www.cncf.io/blog/2022/0T1/31/cncf-archives-the-opentracing-project/)
in favor of the [OpenTelemetry project](https://opentelemetry.io/). In this
new release we decided to introduce the [`telemetry`
trait](/camel-k/1.12.x/traits/telemetry.html) based on OpenTelemetry and
deprecate the [`tracing` trait](/cam [...]
+If you are already using Distributed Tracing tools then you might already know
that the [CNCF](https://www.cncf.io) announced that they were [archiving the
OpenTracing
project](https://www.cncf.io/blog/2022/0T1/31/cncf-archives-the-opentracing-project/)
in favor of the [OpenTelemetry project](https://opentelemetry.io/). In this
new release we decided to introduce the [`telemetry`
trait](/camel-k/next/traits/telemetry.html) based on OpenTelemetry and
deprecate the [`tracing` trait](/camel [...]
## Dependencies upgrade
diff --git a/content/blog/2023/03/camel-k-telemetry/index.md
b/content/blog/2023/03/camel-k-telemetry/index.md
index e7c62470..35eed806 100644
--- a/content/blog/2023/03/camel-k-telemetry/index.md
+++ b/content/blog/2023/03/camel-k-telemetry/index.md
@@ -9,7 +9,7 @@ preview: "Camel K: how to configure Distributed Tracing for an
Integration"
Tracing is an important approach for controlling and monitoring the experience
of users, it allows us to gather more information about an integration's
performance.
-Camel K has been providing support for distributed tracing using OpenTracing
since long time. At the beginning of 2022, the [CNCF](https://www.cncf.io)
announced that they were [archiving the OpenTracing
project](https://www.cncf.io/blog/2022/01/31/cncf-archives-the-opentracing-project/)
in favor of the [OpenTelemetry project](https://opentelemetry.io/).
OpenTelemetry is the latest solution created by merging OpenTracing and
OpenCensus. As a result, we decided in Camel K 1.12 to introduc [...]
+Camel K has been providing support for distributed tracing using OpenTracing
since long time. At the beginning of 2022, the [CNCF](https://www.cncf.io)
announced that they were [archiving the OpenTracing
project](https://www.cncf.io/blog/2022/01/31/cncf-archives-the-opentracing-project/)
in favor of the [OpenTelemetry project](https://opentelemetry.io/).
OpenTelemetry is the latest solution created by merging OpenTracing and
OpenCensus. As a result, we decided in Camel K 1.12 to introduc [...]
I'll walk you through the configurations needed to support Distributed tracing
for your Camel integrations in this blog post.
@@ -42,7 +42,7 @@ NAME READY STATUS
RESTARTS AGE
camel-k-operator-5b897ddcdd-4qwqb 1/1 Running 0 50s
```
-For more information see the
[documentation](/camel-k/1.12.x/installation/installation.html)
+For more information see the
[documentation](/camel-k/next/installation/installation.html)
## Install Jaeger
diff --git a/content/blog/2023/04/camel-observation/index.md
b/content/blog/2023/04/camel-observation/index.md
index 81c09d08..9b0bc2a8 100644
--- a/content/blog/2023/04/camel-observation/index.md
+++ b/content/blog/2023/04/camel-observation/index.md
@@ -48,7 +48,7 @@ registry.observationConfig().observationHandler(new
DefaultTracingObservationHan
## How does Micrometer Observation work with Camel?
-Apache Camel comes with an abstraction of a
[`Tracer`](/components/3.20.x/others/tracing.html). It automatically creates
spans for Camel Routes.
+Apache Camel comes with an abstraction of a
[`Tracer`](/components/next/others/tracing.html). It automatically creates
spans for Camel Routes.
With Micrometer Observation there's the modified concept of a `Tracer` to
allow distingushing between high and low cardinality tags. That in turn allows
to use the `Tracer` API to create `Observations` instead of spans. That allows
to automatically create both traces and metrics depending on your
`ObservationRegistry` setup.
diff --git a/content/blog/2023/05/camel-debezium-quarkus/index.md
b/content/blog/2023/05/camel-debezium-quarkus/index.md
index 17114ca5..014bc031 100644
--- a/content/blog/2023/05/camel-debezium-quarkus/index.md
+++ b/content/blog/2023/05/camel-debezium-quarkus/index.md
@@ -38,11 +38,11 @@ This is useful for ETL (Extract, Transform, Load)
processes, as it allows moving
Camel includes components for Debezium in its implementation which allows to
use it inside Apache Camel as a consumer endpoint which allows running the
[Debezium engine in an embedded
way](https://debezium.io/documentation/reference/stable/development/engine.html)
in the running instance of Camel.
Some of the components currently available are:
-- [Debezium MySQL Connector
Component](/components/3.20.x/debezium-mysql-component.html)
-- [Debezium PostgreSQL Connector
Component](/components/3.20.x/debezium-postgres-component.html)
-- [Debezium SQL Server Connector
Component](/components/3.20.x/debezium-sqlserver-component.html)
-- [Debezium MongoDB Connector
Component](/components/3.20.x/debezium-mongodb-component.html)
-- [Debezium Oracle Connector
Component](/components/3.20.x/debezium-oracle-component.html) (So far it is
still not supported in Quarkus)
+- [Debezium MySQL Connector
Component](/components/next/debezium-mysql-component.html)
+- [Debezium PostgreSQL Connector
Component](/components/next/debezium-postgres-component.html)
+- [Debezium SQL Server Connector
Component](/components/next/debezium-sqlserver-component.html)
+- [Debezium MongoDB Connector
Component](/components/next/debezium-mongodb-component.html)
+- [Debezium Oracle Connector
Component](/components/next/debezium-oracle-component.html) (So far it is still
not supported in Quarkus)
Now that we have introduced the different technologies we are going to use,
let's start building our application.
