From edadb8b7f50b5a0c68f6d1be57ec0548bb45c5c6 Mon Sep 17 00:00:00 2001 From: David Mueller Date: Tue, 14 May 2024 16:35:48 -0400 Subject: [PATCH] remove unused file --- .../command/featureUtility-modifications.adoc | 81 ------------------- 1 file changed, 81 deletions(-) delete mode 100644 modules/reference/pages/command/featureUtility-modifications.adoc diff --git a/modules/reference/pages/command/featureUtility-modifications.adoc b/modules/reference/pages/command/featureUtility-modifications.adoc deleted file mode 100644 index 4d1f5b354d..0000000000 --- a/modules/reference/pages/command/featureUtility-modifications.adoc +++ /dev/null @@ -1,81 +0,0 @@ -// -// Copyright (c) 2021 IBM Corporation and others. -// Licensed under Creative Commons Attribution-NoDerivatives -// 4.0 International (CC BY-ND 4.0) -// https://creativecommons.org/licenses/by-nd/4.0/ -// -// Contributors: -// IBM Corporation -// -:page-description: You can modify several behaviors of the `featureUtility` commands by declaring environment variables in the shell environment or by specifying properties in the `featureUtility.properties` file that's located in the `{wlp.install.dir}/etc/` directory. -:seo-title: Repository and proxy modifications - OpenLiberty.io -:seo-description: You can modify several behaviors of the `featureUtility` commands by declaring environment variables in the shell environment or by specifying properties in the `featureUtility.properties` file that's located in the `{wlp.install.dir}/etc/` directory. -:page-layout: general-reference -:page-type: general -= Modifications for featureUtility commands - -You can modify several behaviors of the `featureUtility` commands by declaring environment variables in the shell environment or by specifying properties in the `featureUtility.properties` file that's located in the `{wlp.install.dir}/etc/` directory. - -Properties that are specified in the `featureUtility.properties` file take precedence over environment variables that are declared in the shell environment. -For example, if you specify the `featureLocalRepo` property in the `featureUtility.properties` file, then any value set with the `FEATURE_LOCAL_REPO` environment variable is overridden. -You can specify modifications to the `featureUtility` commands by using properties in the `featureUtility.properties` file rather than environment variables. -You can also easily see Maven repository and proxy settings that are contained in the `featureUtility.properties` file by running the xref:command/featureUtility-viewSettings.adoc[featureUtility viewSettings command]. -Settings that are configured with environment variables don't show up with this information. - -The following table lists the environment variables and their corresponding properties that you can specify to modify the `featureUtility` commands: - -[%header,cols=3*] -|=== -|Environment variable -|Corresponding properties -|Description - -|`FEATURE_REPO_URL` -|`mavenCentralMirror.url` -|Overrides Maven Central with an on-premises Maven repository. - -|`FEATURE_REPO_USER` -|`mavenCentralMirror.user` -|The username for `FEATURE_REPO_URL` user credentials. - -|`FEATURE_REPO_PASSWORD` -|`mavenCentralMirror.password` -|The password for `FEATURE_REPO_URL` user credentials. - -|`FEATURE_LOCAL_REPO` -|`featureLocalRepo` -|Overrides the local Maven repository. - -|`http_proxy` -|`proxyHost`, `proxyPort`, `proxyUser`, and `proxyPassword` -a|Configures the outbound HTTP proxy. - -|`https_proxy` -|`proxyHost`, `proxyPort`, `proxyUser`, and `proxyPassword` -a|Configures the outbound HTTPS proxy. - -|=== -{empty} + - -== Install user features - -You can specify the maven coordinates for the features BOM file to install user features by adding the `customBomFileName.featuresbom` property in the `featureUtility.properties` file, as shown in the following example: - ----- -customBomFileName.featuresbom=my.maven.coordinate:my-features-bom:version ----- - -== Define custom repositories - -You can also define remote repositories by adding the `customRepoName.url` property in the `featureUtility.properties` file. -Each repository name must be unique, and defined repositories are accessed in the order that they're specified. -If a repository requires a username and password, also set the `customRepoName.user` and `customRepoName.password` properties. -In the following example, two custom repositories, `remoteRepo1` and `remoteRepo2`, are defined. -The `remoteRepo2` repository is secure so it also requires a username and password: - ----- -remoteRepo1.url=http://my-remote-server1/maven2 -remoteRepo2.url=https://my-remote-server2/secure/maven2 -remoteRepo2.user=operator -remoteRepo2.password={aes}KM8dhwcv892Ss1sawu9R+ -----