This is an automated email from the ASF dual-hosted git repository.
zregvart pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/camel-website.git
commit af041ee2f7bbe9c1042fc040a8cb771e4c2ed581
Author: Zoran Regvart <zregv...@apache.org>
AuthorDate: Thu Nov 5 15:03:51 2020 +0100
fix: broken links
---
.../2019/12/LanguageSupportTooling-0.0.20/index.md | 2 +-
.../blog/2020/01/CustomWebApiComponent/index.md | 4 +--
.../04/Camel-Quarkus-release-1.0.0-M7/index.md | 2 +-
content/blog/2020/04/Camel32-Whatsnew/index.md | 2 +-
content/blog/2020/04/RELEASE-3.2.0/index.md | 2 +-
content/blog/2020/05/Camel33-Whatsnew/index.md | 2 +-
.../06/camel-quarkus-release-1.0.0-CR2/index.md | 21 ++++++------
content/blog/2020/06/camel34-whatsnew/index.md | 2 +-
.../07/camel-quarkus-release-1.0.0-CR3/index.md | 38 +++++++++++-----------
.../2020/08/camel-quarkus-release-1.0.0/index.md | 11 +++----
10 files changed, 42 insertions(+), 44 deletions(-)
diff --git a/content/blog/2019/12/LanguageSupportTooling-0.0.20/index.md
b/content/blog/2019/12/LanguageSupportTooling-0.0.20/index.md
index eddbfd4..98e4872 100644
--- a/content/blog/2019/12/LanguageSupportTooling-0.0.20/index.md
+++ b/content/blog/2019/12/LanguageSupportTooling-0.0.20/index.md
@@ -12,7 +12,7 @@ Before going into the list of updates in detail, I want to
note that I mentioned
### Camel 3 inside
-Camel 3 was [released](/blog/release-3-0-0.html) a few weeks ago, and the
Camel Language Server is already relying on it internally. What does that mean
for the end user? It means that the default catalog is now using Camel 3.
+Camel 3 was [released](/blog/2019/11/RELEASE-3.0.0/) a few weeks ago, and the
Camel Language Server is already relying on it internally. What does that mean
for the end user? It means that the default catalog is now using Camel 3.
If you are still based on Camel 2.x, no problem; check out the following
awesome feature.
diff --git a/content/blog/2020/01/CustomWebApiComponent/index.md
b/content/blog/2020/01/CustomWebApiComponent/index.md
index 9373b6d..793e42f 100644
--- a/content/blog/2020/01/CustomWebApiComponent/index.md
+++ b/content/blog/2020/01/CustomWebApiComponent/index.md
@@ -7,9 +7,9 @@ categories: ["Usecases"]
preview: "Build your own custom Web API Component from scratch."
---
-Have you built a new great Web API for your product? Wouldn't be wonderful to
have it available as a part of the great [Apache Camel component
family](/components/latest)? We would love it.
+Have you built a new great Web API for your product? Wouldn't be wonderful to
have it available as a part of the great [Apache Camel component
family](/components/latest/)? We would love it.
-The community just released [Camel 3](/blog/Camel3-Whatsnew) which is more
modular, lightweight and already includes lots of components (300+) to quickly
integrate various systems consuming or producing data. All of these components
can be used with the same integration domain specific language (DSL) based on
the famous [Enterprise Integration
Patterns](https://www.enterpriseintegrationpatterns.com) (EIPs).
+The community just released [Camel 3](/blog/2019/12/Camel3-Whatsnew/) which is
more modular, lightweight and already includes lots of components (300+) to
quickly integrate various systems consuming or producing data. All of these
components can be used with the same integration domain specific language (DSL)
based on the famous [Enterprise Integration
Patterns](https://www.enterpriseintegrationpatterns.com) (EIPs).
Creating a new component is actually pretty simple and, as a benefit, you will
also have the possibility to use Camel sub-projects to make your Web API
available within different runtimes:
[SpringBoot](https://github.com/apache/camel-spring-boot) (auto-config),
[Quarkus](https://github.com/apache/camel-quarkus) (Java native compilation)
and [Camel-K](https://github.com/apache/camel-k) (serverless work).
diff --git a/content/blog/2020/04/Camel-Quarkus-release-1.0.0-M7/index.md
b/content/blog/2020/04/Camel-Quarkus-release-1.0.0-M7/index.md
index 71a2793..339a1c6 100644
--- a/content/blog/2020/04/Camel-Quarkus-release-1.0.0-M7/index.md
+++ b/content/blog/2020/04/Camel-Quarkus-release-1.0.0-M7/index.md
@@ -58,7 +58,7 @@ Components promoted from JVM-only to JVM+native:
* Openshift Build Config
* Openshift Builds
-All supported bits can be seen in the [List of Camel Quarkus
extensions](/camel-quarkus/latest/list-of-camel-quarkus-extensions.html).
+All supported bits can be seen in the [List of Camel Quarkus
extensions](/camel-quarkus/latest/reference/index.html).
## Quarkus 1.4.1
diff --git a/content/blog/2020/04/Camel32-Whatsnew/index.md
b/content/blog/2020/04/Camel32-Whatsnew/index.md
index 4e22eb0..8fa4292 100644
--- a/content/blog/2020/04/Camel32-Whatsnew/index.md
+++ b/content/blog/2020/04/Camel32-Whatsnew/index.md
@@ -8,7 +8,7 @@ preview: Details of what we have done in the Camel 3.2 release.
A few days ago Apache Camel 3.2 was released. This is a continuation of the
work we are doing on Camel leading up to the first long term support release
(LTS) that would be either Camel 3.3 or 3.4.
-In case you have missed this, the release model in Camel 3.x is following the
principe of LTS and non-LTS releases (like Java JDKs). For more details see
this [blog post](/blog/LTS-Release-Schedule/).
+In case you have missed this, the release model in Camel 3.x is following the
principe of LTS and non-LTS releases (like Java JDKs). For more details see
this [blog post](/blog/2020/03/LTS-Release-Schedule/).
What this means is that we will not do patch releases for Camel 3.2.x, but
move ahead for Camel 3.3.
diff --git a/content/blog/2020/04/RELEASE-3.2.0/index.md
b/content/blog/2020/04/RELEASE-3.2.0/index.md
index eb908f8..361588f 100644
--- a/content/blog/2020/04/RELEASE-3.2.0/index.md
+++ b/content/blog/2020/04/RELEASE-3.2.0/index.md
@@ -10,7 +10,7 @@ preview: "The Camel community announces the immediate
availability of the new Ca
The Camel community announces the immediate availability of Camel 3.2.0, a new
minor release with over 160 new features, improvements and fixes.
-Please read our [Camel 3.x upgrade
guide](/manual/latest/camel-3x-upgrade-guide.html#_upgrading_camel_3_1_to_3_2)
that describes how to upgrade Camel 3.1 applications to Camel 3.2.
+Please read our [Camel 3.x upgrade
guide](/manual/latest/camel-3x-upgrade-guide-3_2.html) that describes how to
upgrade Camel 3.1 applications to Camel 3.2.
The artifacts are published and ready for you to download from the Central
Maven repository. For more details please take a look at the [release
notes](/releases/release-3.2.0/).
diff --git a/content/blog/2020/05/Camel33-Whatsnew/index.md
b/content/blog/2020/05/Camel33-Whatsnew/index.md
index 21701ef..8376d74 100644
--- a/content/blog/2020/05/Camel33-Whatsnew/index.md
+++ b/content/blog/2020/05/Camel33-Whatsnew/index.md
@@ -8,7 +8,7 @@ preview: Details of what we have done in the Camel 3.3 release.
A few days ago Apache Camel 3.3 was released. This is a continuation of the
work we are doing on Camel leading up to the first long term support release
(LTS) that will be the next release v3.4.
-In case you have missed this, the release model in Camel 3.x is following the
principe of LTS and non-LTS releases (like Java JDKs). For more details see
this [blog post](/blog/LTS-Release-Schedule/).
+In case you have missed this, the release model in Camel 3.x is following the
principe of LTS and non-LTS releases (like Java JDKs). For more details see
this [blog post](/blog/2020/03/LTS-Release-Schedule/).
What this means is that we will not do patch releases for Camel 3.3.x, but
move ahead for Camel 3.4.
diff --git a/content/blog/2020/06/camel-quarkus-release-1.0.0-CR2/index.md
b/content/blog/2020/06/camel-quarkus-release-1.0.0-CR2/index.md
index b2537e8..8366d4a 100644
--- a/content/blog/2020/06/camel-quarkus-release-1.0.0-CR2/index.md
+++ b/content/blog/2020/06/camel-quarkus-release-1.0.0-CR2/index.md
@@ -16,31 +16,31 @@ So what is new in Camel Quarkus 1.0.0-CR2?
While we do not have any new extensions this time, the following extensions
were promoted from JVM-only to JVM+native:
-* [REST OpenApi](/camel-quarkus/latest/extensions/rest-openapi.html)
-* [Avro data format](/camel-quarkus/latest/extensions/avro.html)
-* [MongoDB GridFS](/camel-quarkus/latest/extensions/mongodb-gridfs.html)
-* [Debezium PostgreSQL](/camel-quarkus/latest/extensions/debezium-mysql.html)
-* [Debezium MySQL](/camel-quarkus/latest/extensions/debezium-mysql.html)
+* [REST OpenApi](/camel-quarkus/latest/reference/extensions/rest-openapi.html)
+* [Avro data format](/camel-quarkus/latest/reference/extensions/avro.html)
+* [MongoDB
GridFS](/camel-quarkus/latest/reference/extensions/mongodb-gridfs.html)
+* [Debezium
PostgreSQL](/camel-quarkus/latest/reference/extensions/debezium-mysql.html)
+* [Debezium
MySQL](/camel-quarkus/latest/reference/extensions/debezium-mysql.html)
-All supported bits can be seen in the [List of Camel Quarkus
extensions](/camel-quarkus/latest/list-of-camel-quarkus-extensions.html).
+All supported bits can be seen in the [List of Camel Quarkus
extensions](/camel-quarkus/latest/reference/index.html).
## New documentation pages
Each Camel Quarkus extension has a separate page now. Most of the content is
generated from the data available in
[Camel Catalog](/manual/latest/camel-catalog.html). This includes some basic
description, Maven
coordinates and links to the involved Camel bits.
-[ActiveMQ](/camel-quarkus/latest/extensions/activemq.html) is an example of
such a rudimentary
+[ActiveMQ](/camel-quarkus/latest/reference/extensions/activemq.html) is an
example of such a rudimentary
page.
In some cases, that generated content is combined with manually maintained
sections that inform about Camel
-Quarkus specific behavior, limitations, configuration options, etc. See
[MicroProfile
Health](/camel-quarkus/latest/extensions/microprofile-health.html) as an
example.
+Quarkus specific behavior, limitations, configuration options, etc. See
[MicroProfile
Health](/camel-quarkus/latest/reference/extensions/microprofile-health.html) as
an example.
Within a couple of days, [code.quarkus.io](https://code.quarkus.io/) should
start to reference the new extension pages
as "guides" of the individual Camel entries listed there.
## Camel 3.3.0
-Camel was upgraded to [3.3.0](/blog/Camel33-Whatsnew/) bringing less
reflection and less JAXP to
+Camel was upgraded to [3.3.0](/blog/2020/05/Camel33-Whatsnew/) bringing less
reflection and less JAXP to
Camel Quarkus, thus improving the disk size, startup time and RAM usage of
Camel Quarkus applications.
## Quarkus 1.5.0.Final
@@ -56,9 +56,8 @@ the last release supporting Java 8.
The Hystrix component was recently deprecated in Camel, so we deprecated it as
well. It will be removed in the next
Camel Quarkus release. Please use
-[Microprofile Fault
Tolerance](/camel-quarkus/latest/extensions/microprofile-fault-tolerance.html)
+[Microprofile Fault
Tolerance](/camel-quarkus/latest/reference/extensions/microprofile-fault-tolerance.html)
as a replacement.
Enjoy and give feedback either via [mailing
lists](/manual/latest/mailing-lists.html)
or [GitHub issues](https://github.com/apache/camel-quarkus/issues)!
-
diff --git a/content/blog/2020/06/camel34-whatsnew/index.md
b/content/blog/2020/06/camel34-whatsnew/index.md
index 44630b3..4ac5c36 100644
--- a/content/blog/2020/06/camel34-whatsnew/index.md
+++ b/content/blog/2020/06/camel34-whatsnew/index.md
@@ -11,7 +11,7 @@ Apache Camel 3.4 is the first LTS (Long Term Support) release
of Camel 3.
This release will be actively supported with regular patch releases containing
important bug and security fixes for 1-year.
-For more details about LTS vs non-LTS releases see this [blog
post](/blog/LTS-Release-Schedule/).
+For more details about LTS vs non-LTS releases see this [blog
post](/blog/2020/03/LTS-Release-Schedule/).
### So what's in this release?
diff --git a/content/blog/2020/07/camel-quarkus-release-1.0.0-CR3/index.md
b/content/blog/2020/07/camel-quarkus-release-1.0.0-CR3/index.md
index 5da7520..3e8fbc3 100644
--- a/content/blog/2020/07/camel-quarkus-release-1.0.0-CR3/index.md
+++ b/content/blog/2020/07/camel-quarkus-release-1.0.0-CR3/index.md
@@ -16,29 +16,29 @@ Here are some highlights of Camel Quarkus 1.0.0-CR3.
The following new extensions were added:
-* [AWS 2 Athena](/camel-quarkus/latest/extensions/aws2-athena.html)
-* [Component DSL](/camel-quarkus/latest/extensions/componentdsl.html)
-* [JOLT](/camel-quarkus/latest/extensions/jolt.html)
-* [JTA](/camel-quarkus/latest/extensions/jta.html)
-* [OpenApi Java](/camel-quarkus/latest/extensions/openapi-java.html)
-* [Tika](/camel-quarkus/latest/extensions/tika.html)
-* [Vert.x](/camel-quarkus/latest/extensions/vertx.html)
+* [AWS 2 Athena](/camel-quarkus/latest/reference/extensions/aws2-athena.html)
+* [Component DSL](/camel-quarkus/latest/reference/extensions/componentdsl.html)
+* [JOLT](/camel-quarkus/latest/reference/extensions/jolt.html)
+* [JTA](/camel-quarkus/latest/reference/extensions/jta.html)
+* [OpenApi Java](/camel-quarkus/latest/reference/extensions/openapi-java.html)
+* [Tika](/camel-quarkus/latest/reference/extensions/tika.html)
+* [Vert.x](/camel-quarkus/latest/reference/extensions/vertx.html)
The following extensions added native mode support:
-* [AWS 2 DynamoDB Streams](/camel-quarkus/latest/extensions/aws2-ddb.html)
-* [AWS 2 Elastic Compute Cloud
(EC2)](/camel-quarkus/latest/extensions/aws2-ec2.html)
-* [AWS 2 Elastic Container Service
(ECS)](/camel-quarkus/latest/extensions/aws2-ecs.html)
-* [AWS 2 Elastic Kubernetes Service
(EKS)](/camel-quarkus/latest/extensions/aws2-eks.html)
-* [AWS 2 Identity and Access Management
(IAM)](/camel-quarkus/latest/extensions/aws2-iam.html)
-* [AWS 2 Key Management Service
(KMS)](/camel-quarkus/latest/extensions/aws2-kms.html)
-* [AWS 2 Managed Streaming for Apache Kafka
(MSK)](/camel-quarkus/latest/extensions/aws2-msk.html)
-* [AWS 2 MQ](/camel-quarkus/latest/extensions/aws2-mq.html)
-* [AWS 2 Simple Email Service
(SES)](/camel-quarkus/latest/extensions/aws2-ses.html)
-* [AWS 2 Translate](/camel-quarkus/latest/extensions/aws2-translate.html)
-
-All supported extensions can be seen in the [List of Camel Quarkus
extensions](/camel-quarkus/latest/list-of-camel-quarkus-extensions.html).
+* [AWS 2 DynamoDB
Streams](/camel-quarkus/latest/reference/extensions/aws2-ddb.html)
+* [AWS 2 Elastic Compute Cloud
(EC2)](/camel-quarkus/latest/reference/extensions/aws2-ec2.html)
+* [AWS 2 Elastic Container Service
(ECS)](/camel-quarkus/latest/reference/extensions/aws2-ecs.html)
+* [AWS 2 Elastic Kubernetes Service
(EKS)](/camel-quarkus/latest/reference/extensions/aws2-eks.html)
+* [AWS 2 Identity and Access Management
(IAM)](/camel-quarkus/latest/reference/extensions/aws2-iam.html)
+* [AWS 2 Key Management Service
(KMS)](/camel-quarkus/latest/reference/extensions/aws2-kms.html)
+* [AWS 2 Managed Streaming for Apache Kafka
(MSK)](/camel-quarkus/latest/reference/extensions/aws2-msk.html)
+* [AWS 2 MQ](/camel-quarkus/latest/reference/extensions/aws2-mq.html)
+* [AWS 2 Simple Email Service
(SES)](/camel-quarkus/latest/reference/extensions/aws2-ses.html)
+* [AWS 2
Translate](/camel-quarkus/latest/reference/extensions/aws2-translate.html)
+
+All supported extensions can be seen in the [List of Camel Quarkus
extensions](/camel-quarkus/latest/reference/).
## Camel 3.4.0
diff --git a/content/blog/2020/08/camel-quarkus-release-1.0.0/index.md
b/content/blog/2020/08/camel-quarkus-release-1.0.0/index.md
index 6becec4..330a139 100644
--- a/content/blog/2020/08/camel-quarkus-release-1.0.0/index.md
+++ b/content/blog/2020/08/camel-quarkus-release-1.0.0/index.md
@@ -49,7 +49,7 @@ Camel 3.4, Camel Quarkus supports:
* 17 out of 42 miscellaneous Camel components (40%)
Some of these are supported in JVM mode only - please refer to the
-[complete list](/camel-quarkus/latest/list-of-camel-quarkus-extensions.html)
for details.
+[complete list](/camel-quarkus/latest/reference/index.html) for details.
## Bootstrapping methods
@@ -95,7 +95,7 @@ On Camel Quarkus, the extensions roughly correspond to camel
components - i.e. i
need `camel-sql` you add the `camel-quarkus-sql` extension as a dependency to
your application and it takes
care for both pulling the `camel-sql` artifact and configuring the native
compiler. Extension pages document any
further configuration that needs to be done by the application developer. E.g.
in case of the
-[SQL
extension](/camel-quarkus/latest/extensions/sql.html#_additional_camel_quarkus_configuration),
+[SQL
extension](/camel-quarkus/latest/reference/extensions/sql.html#_additional_camel_quarkus_configuration),
the `quarkus.camel.sql.script-files` property needs to be set.
Check the [Native mode](/camel-quarkus/latest/user-guide/native-mode.html)
section of the Camel
@@ -107,7 +107,7 @@ details about the native compilation on Quarkus.
While we mostly have only indirect information about the usage via
[GitHub issues](https://github.com/apache/camel-quarkus/issues), there is one
prominent user, we are especially proud
of: [Camel K](/camel-k/latest/index.html). As of
-[Camel K
1.0](/blog/2020/06/camel-k-release-1.0.0#fast-startup-and-low-memory), Camel
Quarkus is
+[Camel K
1.0](/blog/2020/06/camel-k-release-1.0.0/#fast-startup-and-low-memory), Camel
Quarkus is
one of the two supported runtimes and "is expected to be the default
underlying runtime in the next release".
## Highlights of the release 1.0.0
@@ -119,8 +119,8 @@ General:
New extensions:
-* [Grok](/camel-quarkus/latest/extensions/grok.html)
-* [JPA](/camel-quarkus/latest/extensions/jpa.html)
+* [Grok](/camel-quarkus/latest/reference/extensions/grok.html)
+* [JPA](/camel-quarkus/latest/reference/extensions/jpa.html)
## What's next?
@@ -129,4 +129,3 @@ New extensions:
* Even less reflection with Camel 3.5
We wish you a lot of joy with Camel Quarkus and we look forward to your
feedback and participation!
-
