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

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


The following commit(s) were added to refs/heads/master by this push:
     new 349cc1b  Give code blocks a real language instead of unknown
349cc1b is described below

commit 349cc1b6618c4d46447fdf156dcc4aef01ae5554
Author: Sylwester Lachiewicz <[email protected]>
AuthorDate: Sun Nov 1 15:16:44 2026 +0000

    Give code blocks a real language instead of unknown
---
 src/site/markdown/examples/deploy-network-issues.md            | 6 +++---
 src/site/markdown/examples/deploying-in-legacy-layout.md.vm    | 6 +++---
 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 ++++----
 7 files changed, 16 insertions(+), 16 deletions(-)

diff --git a/src/site/markdown/examples/deploy-network-issues.md 
b/src/site/markdown/examples/deploy-network-issues.md
index 3d6ad66..01d2606 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
 ```
 
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 48f8116..fa1d220 100644
--- a/src/site/markdown/examples/deploying-in-legacy-layout.md.vm
+++ b/src/site/markdown/examples/deploying-in-legacy-layout.md.vm
@@ -28,7 +28,7 @@ date: 2006-06-21
 
 - legacy layout directory structure:
 
-    ```unknown
+    ```text
       groupId
       |--artifactId
          |--jars
@@ -37,7 +37,7 @@ date: 2006-06-21
 
 - default layout directory structure:
 
-    ```unknown
+    ```text
       groupId
       |--artifactId
          |--version
@@ -47,7 +47,7 @@ date: 2006-06-21
 
     In able to deploy an artifact in a legacy layout of repository, set the 
**repositoryLayout** parameter to `legacy` value\.
 
-    ```unknown
+    ```bash
     mvn 
${project.groupId}:${project.artifactId}:${project.version}:deploy-file 
-Durl=file:///C:/m2-repo \
                                                                                
 -DrepositoryId=some.id \
                                                                                
 -Dfile=your-artifact-1.0.jar \
diff --git a/src/site/markdown/examples/deploying-sources-javadoc.md.vm 
b/src/site/markdown/examples/deploying-sources-javadoc.md.vm
index 88f7f2b..247bf41 100644
--- a/src/site/markdown/examples/deploying-sources-javadoc.md.vm
+++ b/src/site/markdown/examples/deploying-sources-javadoc.md.vm
@@ -24,7 +24,7 @@ date: 20011-02-23
 
 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
@@ -32,7 +32,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 7b12b67..c0c7b4e 100644
--- a/src/site/markdown/examples/deploying-with-classifiers.md.vm
+++ b/src/site/markdown/examples/deploying-with-classifiers.md.vm
@@ -34,7 +34,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=http://localhost:8081/repomanager/ \
                                                                             
-DrepositoryId=some.id \
                                                                             
-Dfile=path/to/artifact-name-1.0.jar \
@@ -46,7 +46,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=http://localhost:8081/repomanager/ \
                                                                             
-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 33dce41..8a7b13e 100644
--- a/src/site/markdown/examples/deploying-with-customized-pom.md.vm
+++ b/src/site/markdown/examples/deploying-with-customized-pom.md.vm
@@ -26,7 +26,7 @@ date: 2006-06-21
 
 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 863576a..5e786dd 100644
--- a/src/site/markdown/examples/disabling-generic-pom.md.vm
+++ b/src/site/markdown/examples/disabling-generic-pom.md.vm
@@ -26,7 +26,7 @@ date: 2006-06-21
 
 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 8a89257..c78fb3e 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\. Additionally, you can 
specify what layout your repository  [...]
 
-```unknown
+```bash
 mvn deploy:deploy-file -Durl=file://C:\m2-repo \
                        -DrepositoryId=some.id \
                        -Dfile=your-artifact-1.0.jar \

Reply via email to