This is an automated email from the ASF dual-hosted git repository.

slachiewicz pushed a commit to branch maven-deploy-plugin-4.x
in repository https://gitbox.apache.org/repos/asf/maven-deploy-plugin.git


The following commit(s) were added to refs/heads/maven-deploy-plugin-4.x by 
this push:
     new cff8537  Give code blocks a real language instead of unknown
cff8537 is described below

commit cff8537862f6c3c97657cb0c986af5971a914490
Author: Sylwester Lachiewicz <[email protected]>
AuthorDate: Mon Nov 2 14:10:53 2026 +0000

    Give code blocks a real language instead of unknown
---
 src/site/markdown/examples/deploy-ftp.md                       |  6 +++---
 src/site/markdown/examples/deploy-http.md                      |  4 ++--
 src/site/markdown/examples/deploy-network-issues.md            | 10 +++++-----
 src/site/markdown/examples/deploy-ssh-external.md              |  8 ++++----
 src/site/markdown/examples/deploying-in-legacy-layout.md.vm    |  4 ++--
 src/site/markdown/examples/deploying-sources-javadoc.md.vm     |  4 ++--
 src/site/markdown/examples/deploying-with-classifiers.md.vm    |  4 ++--
 src/site/markdown/examples/deploying-with-customized-pom.md.vm |  2 +-
 src/site/markdown/examples/disabling-generic-pom.md.vm         |  2 +-
 src/site/markdown/usage.md                                     |  8 ++++----
 10 files changed, 26 insertions(+), 26 deletions(-)

diff --git a/src/site/markdown/examples/deploy-ftp.md 
b/src/site/markdown/examples/deploy-ftp.md
index a6e024c..e4e7417 100644
--- a/src/site/markdown/examples/deploy-ftp.md
+++ b/src/site/markdown/examples/deploy-ftp.md
@@ -36,7 +36,7 @@ transport does not support FTP at all: you must switch to the 
wagon transport
 
 In order to deploy artifacts using FTP you must first specify the use of an 
FTP server in the **distributionManagement** element of your POM as well as 
specifying an `extension` in your `build` element which will pull in the FTP 
artifacts required to deploy with FTP:
 
-```unknown
+```xml
 <project>
   ...
   <distributionManagement>
@@ -62,7 +62,7 @@ In order to deploy artifacts using FTP you must first specify 
the use of an FTP
 
 Your `settings.xml` would contain a `server` element where the `id` of that 
element matches `id` of the FTP repository specified in the POM above. Store 
the password in [encrypted 
form](https://maven.apache.org/guides/mini/guide-encryption.html) rather than 
as clear text:
 
-```unknown
+```xml
 <settings>
   ...
   <servers>
@@ -78,7 +78,7 @@ Your `settings.xml` would contain a `server` element where 
the `id` of that elem
 
 You should, of course, make sure that you can login into the specified FTP 
server by hand before attempting the deployment with Maven. Once you have 
verified that everything is setup correctly you can now deploy your artifacts 
using Maven:
 
-```unknown
+```bash
 mvn deploy
 ```
 
diff --git a/src/site/markdown/examples/deploy-http.md 
b/src/site/markdown/examples/deploy-http.md
index f795713..edfa1a3 100644
--- a/src/site/markdown/examples/deploy-http.md
+++ b/src/site/markdown/examples/deploy-http.md
@@ -28,7 +28,7 @@ under the License.
 
 In order to deploy artifacts using HTTP(S) you must specify the use of an 
HTTP(S) server in the [**distributionManagement** element of your 
POM](https://maven.apache.org/pom.html#Distribution_Management):
 
-```unknown
+```xml
 <project>
   ...
   <distributionManagement>
@@ -51,7 +51,7 @@ explicitly overridden with 
`-Dmaven.deploy.allowInsecureUrl=true` if you accept
 
 Your `settings.xml` would contain a `server` element where the `id` of that 
element matches `id` of the HTTP(S) repository specified in the POM above. It 
must contain the credentials to be used (in [encrypted 
form](https://maven.apache.org/guides/mini/guide-encryption.html)):
 
-```unknown
+```xml
 <settings>
   ...
   <servers>
diff --git a/src/site/markdown/examples/deploy-network-issues.md 
b/src/site/markdown/examples/deploy-network-issues.md
index abb4a0a..ff6ffd0 100644
--- a/src/site/markdown/examples/deploy-network-issues.md
+++ b/src/site/markdown/examples/deploy-network-issues.md
@@ -34,7 +34,7 @@ There are a few strategies to work around the network issue.
 
 Deploy plugin provides [`retryFailedDeploymentCount` 
parameter](../deploy-mojo.html#retryFailedDeploymentCount) to retry deployment 
multiple times before giving up and returning a failure for the `deploy` goal: 
 
-```unknown
+```xml
 <project>
   [...]
   <build>
@@ -64,13 +64,13 @@ When the network is really not consistent, a deeper 
strategy is to deploy in 2 s
 
 Deploying to a local directory can be done from command line, without changing 
POM, using [`altDeploymentRepository` 
parameter](../deploy-mojo.html#altDeploymentRepository):
 
-```unknown
+```bash
 mvn deploy -DaltDeploymentRepository=local::file:./target/staging-deploy
 ```
 
 or for older 2\.x version of maven-deploy-plugin
 
-```unknown
+```bash
 mvn deploy 
-DaltDeploymentRepository=local::default::file:./target/staging-deploy
 ```
 
@@ -84,7 +84,7 @@ Of course, you can configure the repository in your `pom.xml` 
if you want to go
 
 It can be invoked fully from command line (renaming `-Dwagon.` with 
`wagon.targetId` when [Wagon Maven Plugin 2\.0\.1 will be 
released](https://github.com/mojohaus/wagon-maven-plugin/pull/26)):
 
-```unknown
+```bash
 mvn org.codehaus.mojo:wagon-maven-plugin:2.0.0:merge-maven-repos \
   -Dwagon.source=file:./target/staging-deploy \
   -Dwagon.target=https://... \
@@ -95,7 +95,7 @@ mvn 
org.codehaus.mojo:wagon-maven-plugin:2.0.0:merge-maven-repos \
 
 or more simply with `mvn wagon:merge-maven-repos` with configuration in 
`pom.xml`:
 
-```unknown
+```xml
 <project>
   [...]
   <build>
diff --git a/src/site/markdown/examples/deploy-ssh-external.md 
b/src/site/markdown/examples/deploy-ssh-external.md
index d3a62c5..bcb5687 100644
--- a/src/site/markdown/examples/deploy-ssh-external.md
+++ b/src/site/markdown/examples/deploy-ssh-external.md
@@ -32,7 +32,7 @@ over `scpexe://` requires switching to the wagon transport
 
 In order to deploy artifacts using SSH you must first specify the use of an 
SSH server in the **distributionManagement** element of your POM as well as 
specifying an `extension` in your `build` element which will pull in the SSH 
artifacts required to deploy with SSH:
 
-```unknown
+```xml
 
 <project>
   ...
@@ -59,7 +59,7 @@ In order to deploy artifacts using SSH you must first specify 
the use of an SSH
 
 If you are deploying from Unix or have Cygwin installed you won&apos;t need to 
any additional configuration in your `settings.xml` file as everything will be 
taken from the environment. But if you are on Windows and are using something 
like `plink` then you will need something like the following:
 
-```unknown
+```xml
 
 <settings>
   ...
@@ -81,13 +81,13 @@ If you are deploying from Unix or have Cygwin installed you 
won&apos;t need to a
 
 You should, of course, make sure that you can login into the specified SSH 
server by hand before attempting the deployment with Maven. Once you have 
verified that everything is setup correctly you can now deploy your artifacts 
using Maven:
 
-```unknown
+```bash
 mvn deploy
 ```
 
 Sometimes you may have permissions problems deploying and if so you can set 
the file and directory permissions like so:
 
-```unknown
+```xml
 
  <settings>
    ...
diff --git a/src/site/markdown/examples/deploying-in-legacy-layout.md.vm 
b/src/site/markdown/examples/deploying-in-legacy-layout.md.vm
index 4f53937..199a624 100644
--- a/src/site/markdown/examples/deploying-in-legacy-layout.md.vm
+++ b/src/site/markdown/examples/deploying-in-legacy-layout.md.vm
@@ -30,7 +30,7 @@ under the License.
 
 - legacy layout directory structure:
 
-    ```unknown
+    ```text
       groupId
       |--artifactId
          |--jars
@@ -39,7 +39,7 @@ under the License.
 
 - default layout directory structure:
 
-    ```unknown
+    ```text
       groupId
       |--artifactId
          |--version
diff --git a/src/site/markdown/examples/deploying-sources-javadoc.md.vm 
b/src/site/markdown/examples/deploying-sources-javadoc.md.vm
index c12c56b..0d05231 100644
--- a/src/site/markdown/examples/deploying-sources-javadoc.md.vm
+++ b/src/site/markdown/examples/deploying-sources-javadoc.md.vm
@@ -26,7 +26,7 @@ under the License.
 
 A project may include a main jar and associated sources and javadoc jars.
 
-```unknown
+```text
   artifact-name-1.0.jar
   artifact-name-1.0-sources.jar
   artifact-name-1.0-javadoc.jar
@@ -34,7 +34,7 @@ A project may include a main jar and associated sources and 
javadoc jars.
 
 The sources jar contains the Java sources, and the javadoc jar contains the 
generated javadocs. To include these files in your deployment, set the 
**sources** and **javadoc** parameters to the paths to the sources and javadoc 
jar files.
 
-```unknown
+```bash
 mvn ${project.groupId}:${project.artifactId}:${project.version}:deploy-file 
-Durl=file:///home/me/m2-repo \
                                                                             
-DrepositoryId=some.repo.id \
                                                                             
-Dfile=./path/to/artifact-name-1.0.jar \
diff --git a/src/site/markdown/examples/deploying-with-classifiers.md.vm 
b/src/site/markdown/examples/deploying-with-classifiers.md.vm
index a57af40..f28ecb5 100644
--- a/src/site/markdown/examples/deploying-with-classifiers.md.vm
+++ b/src/site/markdown/examples/deploying-with-classifiers.md.vm
@@ -36,7 +36,7 @@ For example: from the following artifact names, the 
classifier is located betwee
 
 You can deploy the main artifact and the classified artifacts in a single run. 
Let&apos;s assume the original filename for the documentation is `site.pdf`: 
 
-```unknown
+```bash
 mvn ${project.groupId}:${project.artifactId}:${project.version}:deploy-file 
-Durl=https://repomanager.example.com/repo/ \
                                                                             
-DrepositoryId=some.id \
                                                                             
-Dfile=path/to/artifact-name-1.0.jar \
@@ -48,7 +48,7 @@ mvn 
${project.groupId}:${project.artifactId}:${project.version}:deploy-file -Dur
 
 If you only want to deploy the `debug`\-jar and want to keep the classifier, 
you can execute the `deploy-file` like
 
-```unknown
+```bash
 mvn ${project.groupId}:${project.artifactId}:${project.version}:deploy-file 
-Durl=https://repomanager.example.com/repo/ \
                                                                             
-DrepositoryId=some.id \
                                                                             
-Dfile=path-to-your-artifact-jar \
diff --git a/src/site/markdown/examples/deploying-with-customized-pom.md.vm 
b/src/site/markdown/examples/deploying-with-customized-pom.md.vm
index 3bfcc15..cde55d1 100644
--- a/src/site/markdown/examples/deploying-with-customized-pom.md.vm
+++ b/src/site/markdown/examples/deploying-with-customized-pom.md.vm
@@ -28,7 +28,7 @@ under the License.
 
 If there is already an existing pom and want it to be deployed together with 
the 3rd party artifact, set the **pomFile** parameter to the path of the 
pom.xml.
 
-```unknown
+```bash
 mvn ${project.groupId}:${project.artifactId}:${project.version}:deploy-file 
-Durl=file:///C:/m2-repo \
                                                                             
-DrepositoryId=some.id \
                                                                             
-Dfile=path-to-your-artifact-jar \
diff --git a/src/site/markdown/examples/disabling-generic-pom.md.vm 
b/src/site/markdown/examples/disabling-generic-pom.md.vm
index a9d667c..f069ac8 100644
--- a/src/site/markdown/examples/disabling-generic-pom.md.vm
+++ b/src/site/markdown/examples/disabling-generic-pom.md.vm
@@ -28,7 +28,7 @@ under the License.
 
 By default, If no pom is specified during deployment of your 3rd party 
artifact, a generic pom will be generated which contains the minimum required 
elements needed for the pom. In order to disable it, set the **generatePom** 
parameter to `false`.
 
-```unknown
+```bash
 mvn ${project.groupId}:${project.artifactId}:${project.version}:deploy-file 
-Durl=file:///C:/m2-repo \
                                                                             
-DrepositoryId=some.id \
                                                                             
-Dfile=path-to-your-artifact-jar \
diff --git a/src/site/markdown/usage.md b/src/site/markdown/usage.md
index 6a7915a..0c64cab 100644
--- a/src/site/markdown/usage.md
+++ b/src/site/markdown/usage.md
@@ -41,7 +41,7 @@ You do not have to edit this project&apos;s POM if the 
location already comes fr
 
 If your repository is secured, you may also want to configure your 
`settings.xml` file to define corresponding `<server/>` entries which provides 
authentication information. Server entries are matched to the different parts 
of the distributionManagement using their `<id/>` elements. For example, your 
project may have a distributionManagement section similar to the following:
 
-```unknown
+```xml
 [...]
   <distributionManagement>
     <repository>
@@ -55,7 +55,7 @@ If your repository is secured, you may also want to configure 
your `settings.xml
 
 In this case, you can specify a server definition in your `settings.xml` to 
provide authentication information for both of these repositories at once. Your 
server section might look like this:
 
-```unknown
+```xml
 [...]
     <server>
       <id>internal.repo</id>
@@ -69,7 +69,7 @@ Please see the article about [Password 
Encryption](https://maven.apache.org/guid
 
 Once you&apos;ve configured your repository deployment information correctly 
deploying your project&apos;s artifact will only require invocation of the 
`deploy` phase of the build:
 
-```unknown
+```bash
 mvn deploy
 ```
 
@@ -77,7 +77,7 @@ mvn deploy
 
 The `deploy:deploy-file` mojo is used primarily for deploying artifacts, which 
were not built by Maven. The project&apos;s development team may or may not 
provide a POM for the artifact, and in some cases you may want to deploy the 
artifact to an internal remote repository. The deploy-file mojo provides 
functionality covering all of these use cases, and offers a wide range of 
configurability for generating a POM on-the-fly. The full usage statement of 
the deploy-file mojo can be described as:
 
-```unknown
+```bash
 mvn deploy:deploy-file -Durl=file://C:\m2-repo \
                        -DrepositoryId=some.id \
                        -Dfile=your-artifact-1.0.jar \

Reply via email to