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.git
The following commit(s) were added to refs/heads/main by this push:
new fb494d3 Set to next version
fb494d3 is described below
commit fb494d387147fe4508077f9e9ed8152239d423a7
Author: Claus Ibsen <claus.ib...@gmail.com>
AuthorDate: Mon Oct 4 22:28:04 2021 +0200
Set to next version
---
docs/user-manual/modules/ROOT/pages/camel-maven-archetypes.adoc | 4 ++--
dsl/camel-jbang/camel-jbang-main/README.md | 6 +++---
2 files changed, 5 insertions(+), 5 deletions(-)
diff --git a/docs/user-manual/modules/ROOT/pages/camel-maven-archetypes.adoc
b/docs/user-manual/modules/ROOT/pages/camel-maven-archetypes.adoc
index c4d7adf..18ef1f6 100644
--- a/docs/user-manual/modules/ROOT/pages/camel-maven-archetypes.adoc
+++ b/docs/user-manual/modules/ROOT/pages/camel-maven-archetypes.adoc
@@ -64,14 +64,14 @@ The maven coordinates for these archetypes is the following:
If you would like to use an archetype from an unreleased version of
Camel, you just need to let the maven-archetype-plugin know where to
look for it. For example, say someone wanted to create a Java based
-project based on Camel 3.12.0-SNAPSHOT. He'd need to use the following command
+project based on Camel 3.13.0-SNAPSHOT. He'd need to use the following command
[source,bash]
----
mvn archetype:generate \
-DarchetypeGroupId=org.apache.camel.archetypes \
-DarchetypeArtifactId=camel-archetype-java \
- -DarchetypeVersion=3.12.0-SNAPSHOT
+ -DarchetypeVersion=3.13.0-SNAPSHOT
----
When the project is created, you may need to add another repository to
diff --git a/dsl/camel-jbang/camel-jbang-main/README.md
b/dsl/camel-jbang/camel-jbang-main/README.md
index b1e0f75..5e59c0a 100644
--- a/dsl/camel-jbang/camel-jbang-main/README.md
+++ b/dsl/camel-jbang/camel-jbang-main/README.md
@@ -80,10 +80,10 @@ Camel, all references to dependencies should use
parameterized ones. Such as:
```
After being processed by antrun, during the build, the aforementioned line
would be transformed to something like (for
-a Camel 3.12.0-SNAPSHOT build):
+a Camel 3.13.0-SNAPSHOT build):
```
-//DEPS org.apache.camel:camel-bom:3.12.0-SNAPSHOT@pom
+//DEPS org.apache.camel:camel-bom:3.13.0-SNAPSHOT@pom
```
The same applies to Camel version references, which should rely on the
`${camel.jbang.version}` parameter (such
@@ -93,7 +93,7 @@ Despite this transformation, the code in `src/main/jbang`
should be valid noneth
and debugging purposes by correctly resolving the parameterized variables on
the command line. Such as:
```
-jbang -Dcamel.jbang.version=3.12.0-SNAPSHOT
-Dcamel.jbang.log4j2.version=2.13.3 -Dcamel.jbang.picocli.version=4.5.0
CamelJBang.java
+jbang -Dcamel.jbang.version=3.13.0-SNAPSHOT
-Dcamel.jbang.log4j2.version=2.13.3 -Dcamel.jbang.picocli.version=4.5.0
CamelJBang.java
```
Alternatively, it is possible to just build the module and then execute the
post-processed script on the `dist` directory.
