diff --git a/docs/en/migrate-scm-manager-from-v1.md b/docs/en/migrate-scm-manager-from-v1.md index 84eebb5ead..d12e1de7b8 100644 --- a/docs/en/migrate-scm-manager-from-v1.md +++ b/docs/en/migrate-scm-manager-from-v1.md @@ -37,7 +37,7 @@ In the figure you can see an example of the page. We tried to guess meaningful n The probably most safe strategy (but also the most costly) is *COPY*. The old folder of the repository will be kept and all data will be copied to the new default folder (so this also is the default). *MOVE* and *INLINE* are more efficient. When you have a lot of repositories, maybe you will take the chance to clean them up and *IGNORE* or even *DELETE* old stuff. -If you have more than 100 Repositories to migrate, you may have to adapt some configuration and increase the limit of jetty form keys. You can do this by setting the `maxFormKeys` and `maxFormContentSize` of the webapp in `conf/serverserver-config.xml`. You have to add the keys to the `WebAppContext` with the id `"scm-webapp"` e.g.: +If you have more than 100 Repositories to migrate, you may have to adapt some configuration and increase the limit of jetty form keys. You can do this by setting the `maxFormKeys` and `maxFormContentSize` of the webapp in `conf/server-config.xml`. You have to add the keys to the `WebAppContext` with the id `"scm-webapp"` e.g.: ``` diff --git a/scm-packaging/helm/src/main/build/repository.groovy b/scm-packaging/helm/src/main/build/repository.groovy index 33021393f8..a1bd43b8cf 100644 --- a/scm-packaging/helm/src/main/build/repository.groovy +++ b/scm-packaging/helm/src/main/build/repository.groovy @@ -1,4 +1,4 @@ -/* +/** * MIT License * * Copyright (c) 2020-present Cloudogu GmbH and Contributors @@ -21,7 +21,6 @@ * OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE * SOFTWARE. */ - def repository = "https://packages.scm-manager.org/repository/helm-v2-releases/" def version = project.version if (version.contains("SNAPSHOT")) {