This is an automated email from the ASF dual-hosted git repository.
astefanutti pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/camel-k.git
commit e25d59c0f54e1853249bd8d9f9d186f7c8dbc102
Author: Antonin Stefanutti <anto...@stefanutti.fr>
AuthorDate: Thu Apr 1 15:17:04 2021 +0200
chore: Remove Maven configuration section from README
---
README.adoc | 88 -------------------------------------------------------------
1 file changed, 88 deletions(-)
diff --git a/README.adoc b/README.adoc
index d8e61c4..1fe75e7 100644
--- a/README.adoc
+++ b/README.adoc
@@ -167,94 +167,6 @@ As example if you want to change the queue size of the
seda component, you can u
camel.component.seda.queueSize = 10
```
-==== Configure Maven settings
-
-Maven settings can be configured by providing a custom settings.xml through a
ConfigMap or secret.
-The source for maven settings can be configured using either the `kamel` CLI
at installation time or by editing Camel K's IntegrationPlatform:
-
-- cli:
-+
-.Syntax
-[source]
-----
-kamel install --maven-settings=configmap|secret:name[/key]
-----
-+
-.Example
-[source]
-----
-kamel cmd --maven-settings=configmap:maven-settings/settings.xml
-----
-
-- IntegrationPlatform:
-+
-[source,yaml]
-----
-apiVersion: camel.apache.org/v1
-kind: IntegrationPlatform
-metadata:
- labels:
- app: camel-k
- name: camel-k
-spec:
- build:
- maven:
- settings:
- configMapKeyRef:
- key: settings.xml
- name: maven-settings
-----
-
-To quickly create a config map you can use the following command:
-
-[source]
-----
-kubectl create configmap maven-settings --from-file=settings.xml
-----
-
-
-As an installation shortcut, additional maven repositories can be
alternatively added using the `--maven-repository` option
-
-
-[source]
-----
-kamel cmd --maven-repository http://repo1.my-company.com --maven-repository
http://repo2.my-company.com
-----
-
-A repository url follows conventions used to configure additional repositories
in https://karaf.apache.org[_Apache Karaf_] so it can be appended with zero or
more of the following flags:
-
-* **@snapshots**: the repository contains snapshots
-* **@noreleases**: the repository does not contain any released artifacts
-* **@id=repository.id**: the id for the repository
-
-[source]
-----
-kamel install --maven-repository
http://repository.apache.org/content/groups/snapshots-group@id=apache@snapshots@noreleases
-----
-
-This results in:
-
-[source,xml]
-----
-<repositories>
- <repository>
- <id>apache</id>
- <url>http://repository.apache.org/content/groups/snapshots-group</url>
- <snapshots>
- <enabled>true</enabled>
- </snapshots>
- <releases>
- <enabled>false</enabled>
- </releases>
- </repository>
-</repositories>
-----
-
-IMPORTANT
-====
-the options `--maven-settings` and `--maven-repository` are mutually exclusive
-====
-
==== Configure Integration Volumes
It's possible to mount persistent volumes into integration containers by using
the `-v` or `--volume` flag. The format of volume flag value is similar to that
of the docker CLI. But instead of specifying a host path to mount from, you
reference the name of a `PersistentVolumeClaim` that you have already
configured within the cluster. E.g
