- Sort Score
- Result 10 results
- Languages All
Results 131 - 140 of 7,991 for Export (0.21 sec)
-
pom.xml
<Bundle-Vendor>CodeLibs</Bundle-Vendor> <Bundle-SymbolicName>org.codelibs.jcifs</Bundle-SymbolicName> <Export-Package> jcifs.internal*;version="${osgi.pkg.version}";x-internal:=true, jcifs*;version="${osgi.pkg.version}", </Export-Package> <Private-Package /> <Import-Package> jakarta.servlet*;resolution:=optional, com.sun.security.jgss;resolution:=optional,
Registered: Sat Dec 20 13:44:44 UTC 2025 - Last Modified: Mon Aug 25 14:34:10 UTC 2025 - 12.1K bytes - Viewed (0) -
helm-releases/minio-1.0.2.tgz
.Values.service.type "ClusterIP" "NodePort" }} Minio can be accessed via port {{ .Values.service.port }} on the following DNS name from within your cluster: {{ template "minio.fullname" . }}.{{ .Release.Namespace }}.svc.cluster.local To access Minio from localhost, run the below commands: 1. export POD_NAME=$(kubectl get pods --namespace {{ .Release.Namespace }} -l "release={{ .Release.Name }}" -o jsonpath="{.items[0].metadata.name}") 2. kubectl port-forward $POD_NAME 9000 --namespace {{ .Release.Namespace }}...
Registered: Sun Dec 28 19:28:13 UTC 2025 - Last Modified: Tue Aug 24 18:58:05 UTC 2021 - 13.6K bytes - Viewed (0) -
helm-releases/minio-3.1.9.tgz
.Values.service.type "ClusterIP" "NodePort" }} Minio can be accessed via port {{ .Values.service.port }} on the following DNS name from within your cluster: {{ template "minio.fullname" . }}.{{ .Release.Namespace }}.svc.cluster.local To access Minio from localhost, run the below commands: 1. export POD_NAME=$(kubectl get pods --namespace {{ .Release.Namespace }} -l "release={{ .Release.Name }}" -o jsonpath="{.items[0].metadata.name}") 2. kubectl port-forward $POD_NAME 9000 --namespace {{ .Release.Namespace }}...
Registered: Sun Dec 28 19:28:13 UTC 2025 - Last Modified: Sun Oct 10 21:28:04 UTC 2021 - 14.6K bytes - Viewed (0) -
helm-releases/minio-3.3.0.tgz
.Values.service.type "ClusterIP" "NodePort" }} Minio can be accessed via port {{ .Values.service.port }} on the following DNS name from within your cluster: {{ template "minio.fullname" . }}.{{ .Release.Namespace }}.svc.cluster.local To access Minio from localhost, run the below commands: 1. export POD_NAME=$(kubectl get pods --namespace {{ .Release.Namespace }} -l "release={{ .Release.Name }}" -o jsonpath="{.items[0].metadata.name}") 2. kubectl port-forward $POD_NAME 9000 --namespace {{ .Release.Namespace }}...
Registered: Sun Dec 28 19:28:13 UTC 2025 - Last Modified: Thu Nov 25 17:33:26 UTC 2021 - 14.6K bytes - Viewed (0) -
docs/en/docs/environment-variables.md
//// tab | Linux, macOS, Windows Bash <div class="termy"> ```console // You could create an env var MY_NAME with $ export MY_NAME="Wade Wilson" // Then you could use it with other programs, like $ echo "Hello $MY_NAME" Hello Wade Wilson ``` </div> //// //// tab | Windows PowerShell <div class="termy">
Registered: Sun Dec 28 07:19:09 UTC 2025 - Last Modified: Sun Aug 31 09:15:41 UTC 2025 - 8.1K bytes - Viewed (0) -
android/guava/pom.xml
<_fixupmessages>^Classes found in the wrong directory: .*</_fixupmessages> <Export-Package> !com.google.common.base.internal, !com.google.common.util.concurrent.internal, !META-INF.*, com.google.common.* </Export-Package> <Import-Package> com.google.common.util.concurrent.internal,
Registered: Fri Dec 26 12:43:10 UTC 2025 - Last Modified: Mon Nov 17 21:36:50 UTC 2025 - 9.8K bytes - Viewed (0) -
docs/debugging/README.md
### Remotely Inspecting backend data
Registered: Sun Dec 28 19:28:13 UTC 2025 - Last Modified: Tue Aug 12 18:20:36 UTC 2025 - 8.6K bytes - Viewed (0) -
ci/official/wheel.sh
python_bin="python" fi tfrun "$python_bin" tensorflow/tools/ci_build/update_version.py --nightly # replace tensorflow to tf_nightly in the wheel name export TFCI_BUILD_PIP_PACKAGE_WHEEL_NAME_ARG="$(echo $TFCI_BUILD_PIP_PACKAGE_WHEEL_NAME_ARG | sed 's/tensorflow/tf_nightly/')" export TFCI_BUILD_PIP_PACKAGE_ADDITIONAL_WHEEL_NAMES="$(echo $TFCI_BUILD_PIP_PACKAGE_ADDITIONAL_WHEEL_NAMES | sed 's/tensorflow/tf_nightly/g')" fi
Registered: Tue Dec 30 12:39:10 UTC 2025 - Last Modified: Mon Mar 03 17:29:53 UTC 2025 - 3.8K bytes - Viewed (0) -
helm-releases/minio-3.3.3.tgz
.Values.service.type "ClusterIP" "NodePort" }} MinIO can be accessed via port {{ .Values.service.port }} on the following DNS name from within your cluster: {{ template "minio.fullname" . }}.{{ .Release.Namespace }}.svc.cluster.local To access MinIO from localhost, run the below commands: 1. export POD_NAME=$(kubectl get pods --namespace {{ .Release.Namespace }} -l "release={{ .Release.Name }}" -o jsonpath="{.items[0].metadata.name}") 2. kubectl port-forward $POD_NAME 9000 --namespace {{ .Release.Namespace }}...
Registered: Sun Dec 28 19:28:13 UTC 2025 - Last Modified: Sat Dec 11 17:28:02 UTC 2021 - 14.6K bytes - Viewed (0) -
helm-releases/minio-3.4.7.tgz
.Values.service.type "ClusterIP" "NodePort" }} MinIO can be accessed via port {{ .Values.service.port }} on the following DNS name from within your cluster: {{ template "minio.fullname" . }}.{{ .Release.Namespace }}.svc.cluster.local To access MinIO from localhost, run the below commands: 1. export POD_NAME=$(kubectl get pods --namespace {{ .Release.Namespace }} -l "release={{ .Release.Name }}" -o jsonpath="{.items[0].metadata.name}") 2. kubectl port-forward $POD_NAME 9000 --namespace {{ .Release.Namespace }}...
Registered: Sun Dec 28 19:28:13 UTC 2025 - Last Modified: Tue Jan 25 20:49:24 UTC 2022 - 15.2K bytes - Viewed (0)