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
The following commit(s) were added to refs/heads/master by this push:
new 2e69f10 fix: cleanup release notes
2e69f10 is described below
commit 2e69f108a45c5c3d183087a6774a01a9c87f4472
Author: Zoran Regvart <[email protected]>
AuthorDate: Wed Jul 24 13:24:22 2019 +0200
fix: cleanup release notes
---
content/releases/release-2.18.0.md | 8 ++++----
content/releases/release-2.20.0.md | 8 ++++----
2 files changed, 8 insertions(+), 8 deletions(-)
diff --git a/content/releases/release-2.18.0.md
b/content/releases/release-2.18.0.md
index 0c7b58b..b03340e 100644
--- a/content/releases/release-2.18.0.md
+++ b/content/releases/release-2.18.0.md
@@ -18,8 +18,8 @@ fixes.
the camel-example-java8.
We love feedback on this DSL and expect to improved the API over the
next couple of releases.
-* The XSD schema for <camelContext> and its other configuration elements
-are now also documented (before it was only <routes> and <rests>). The
+* The XSD schema for `<camelContext>` and its other configuration elements
+are now also documented (before it was only `<routes>` and `<rests>`). The
XSD schema now also documents the default values of all the options.
* Introduced `FluentProducerTemplate` using fluent builder style as a
alternative to ProducerTemplate
@@ -115,7 +115,7 @@ or a list of entities as the result.
using Simple language parameters, now avoids an intermediate
conversion of the parameters to a String value. This ensures the passed
in values when calling the bean method is using the parameter type as-is
-from <<simple-language,Simple>>.
+from Simple language.
* Camel CDI now supports importing Camel XML
configuration files
* Camel CDI does not deploy an empty Camel context bean
@@ -166,7 +166,7 @@ used when querying the catalog. There is a
`camel-catalog-maven` module
that is able to download catalog JARs from Maven central.
* A new Camel Attachment interface was added that allows propagating
headers for attachments. Camel CXF, Camel
-Mail (including the <<mime-multipart-dataformat,MIME-Multipart>>data
+Mail (including the MIME-Multipart data
format), and Camel-Jetty set and consume attachment
headers.
* Improved bean method call to validate if method name
diff --git a/content/releases/release-2.20.0.md
b/content/releases/release-2.20.0.md
index 3771c15..a1bcf85 100644
--- a/content/releases/release-2.20.0.md
+++ b/content/releases/release-2.20.0.md
@@ -25,7 +25,7 @@ files (application.properties|yaml file) when you configure
any of the
Camel starter components.
* Camel Spring Boot now also supports using
Spring (auto) configuration to configure CamelContext when using Spring
-XML files with <camelContext>.
+XML files with `<camelContext>`.
* Worked to make Apache Camel more ready and compatible with the
upcoming Spring Boot 2 and Spring Framework 5. Officially support for
these is expected in Camel 2.21 release.
@@ -182,11 +182,11 @@ explicit.
explicit configure a registry to be used, or turn it on via management
agent, or set the statics level to extended mode.
* Camel with Spring XML routes will no longer register endpoints in the
-Spring registry from Camel routes where <from> or <to> have endpoints
+Spring registry from Camel routes where `<from>` or `<to>` have endpoints
assigned with an explicit id attribute. The
-option registerEndpointIdsFromRoute can be set to true on <camelContext>
+option registerEndpointIdsFromRoute can be set to true on `<camelContext>`
to be backwards compatible. However this registration is deprecated,
-instead you should use <endpoint> to register Camel endpoints with id's
+instead you should use `<endpoint>` to register Camel endpoints with id's
in Spring registry.
* camel-spring-dm has been removed as it was not working properly anyway
and was deprecated some releases ago. For XML DSL with OSGi use
