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-scm.git


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

commit 177ab0855fec8b9a2140c72d9bf99e754d24f20e
Author: Sylwester Lachiewicz <[email protected]>
AuthorDate: Sun Nov 1 15:18:13 2026 +0000

    Give code blocks a real language instead of unknown
---
 maven-scm-client/src/site/markdown/index.md        |  4 +--
 .../markdown/examples/bootstrapping-with-pom.md.vm |  6 ++--
 .../markdown/examples/scm-advance-features.md.vm   | 32 +++++++++++-----------
 maven-scm-plugin/src/site/markdown/usage.md        | 12 ++++----
 src/site/markdown/guide/new_provider.md            | 10 +++----
 src/site/markdown/guide/usage.md                   | 12 ++++----
 6 files changed, 38 insertions(+), 38 deletions(-)

diff --git a/maven-scm-client/src/site/markdown/index.md 
b/maven-scm-client/src/site/markdown/index.md
index caf15fad5..ef7975227 100644
--- a/maven-scm-client/src/site/markdown/index.md
+++ b/maven-scm-client/src/site/markdown/index.md
@@ -29,7 +29,7 @@ The Maven SCM client is a simple SCM command line tool.
 
 ## Usage
 
-```unknown
+```shell
 # java -jar target\maven-scm-client-1.1-jar-with-dependencies.jar
 Usage: maven-scm-client <command> <working directory> <scm url> [<scmVersion> 
[<scmVersionType>]]
 scmVersion is a branch name/tag name/revision number.
@@ -38,7 +38,7 @@ scmVersionType can be 'branch', 'tag', 'revision'. The 
default value is 'revisio
 
 ## Example
 
-```unknown
+```shell
 # java -jar target\maven-scm-client-1.1-jar-with-dependencies.jar checkout 
c:\temp\maven-scm-client 
scm:svn:http://svn.apache.org/repos/asf/maven/scm/trunk/maven-scm-client
 [INFO] Executing: cmd.exe /X /C "svn --non-interactive checkout 
http://svn.apache.org/repos/asf/maven/scm/trunk/maven-scm-client 
maven-scm-client"
 [INFO] Working directory: c:\temp
diff --git 
a/maven-scm-plugin/src/site/markdown/examples/bootstrapping-with-pom.md.vm 
b/maven-scm-plugin/src/site/markdown/examples/bootstrapping-with-pom.md.vm
index 9b09c9e5f..91fe17704 100644
--- a/maven-scm-plugin/src/site/markdown/examples/bootstrapping-with-pom.md.vm
+++ b/maven-scm-plugin/src/site/markdown/examples/bootstrapping-with-pom.md.vm
@@ -29,7 +29,7 @@ Using the `scm:bootstrap` a project can be build from a fresh 
copy of the source
 
 The `pom.xml` should contain an SCM configuration for the bootstrap to work.
 
-```unknown
+```xml
 <project>
   ...
   <packaging>jar</packaging>
@@ -62,13 +62,13 @@ The `pom.xml` should contain an SCM configuration for the 
bootstrap to work.
 
 Assuming the SCM configuration has been configured in the `pom.xml`, 
bootstrapping can be invoked by
 
-```unknown
+```bash
    mvn scm:bootstrap
 ```
 
 or in case of a multi-module project, bootstrapping should be invoked as
 
-```unknown
+```bash
    mvn scm:bootstrap -N
 ```
 
diff --git 
a/maven-scm-plugin/src/site/markdown/examples/scm-advance-features.md.vm 
b/maven-scm-plugin/src/site/markdown/examples/scm-advance-features.md.vm
index 01aca6ae8..aaed480e9 100644
--- a/maven-scm-plugin/src/site/markdown/examples/scm-advance-features.md.vm
+++ b/maven-scm-plugin/src/site/markdown/examples/scm-advance-features.md.vm
@@ -27,7 +27,7 @@ under the License.
 
 The SCM plugin requires the SCM to be configured in the `pom.xml`.
 
-```unknown
+```xml
 <project>
   ...
   <packaging>jar</packaging>
@@ -47,7 +47,7 @@ Alternatively you can configure the SCM url also in via 
plugin parameters.
 
 If you want to change the used SCM provider implementation, for example you 
want to use the JGit instead of the CLI based default implementation, you must 
configure your plugin like that:
 
-```unknown
+```xml
 <project>
   ...
   <build>
@@ -78,7 +78,7 @@ changelog - displays the project commit changes for each 
revisions
 
 `pom.xml` configuration :
 
-```unknown
+```xml
 <project>
   ...
   <build>
@@ -103,13 +103,13 @@ changelog - displays the project commit changes for each 
revisions
 
 Command :
 
-```unknown
+```bash
   mvn scm:changelog
 ```
 
 or you can specify the startDate and endDate on the commandline
 
-```unknown
+```bash
   mvn -DstartDate=YYYY-MM-DD -DendDate=YYYY-MM-DD scm:changelog
 ```
 
@@ -118,7 +118,7 @@ diff
 
 `pom.xml` configuration :
 
-```unknown
+```xml
 <project>
   ...
   <build>
@@ -143,13 +143,13 @@ diff
 
 Command :
 
-```unknown
+```bash
    mvn scm:diff
 ```
 
 or you can specify the startRevision and endRevision in the command line
 
-```unknown
+```bash
    mvn -DstartRevision=<revision> -DendRevision=<revision> scm:diff
 ```
 
@@ -158,7 +158,7 @@ edit - set the edit status of the file, locking the project 
sources if supported
 
 Command :
 
-```unknown
+```bash
   mvn scm:edit
 ```
 
@@ -167,7 +167,7 @@ status - displays the modified files in the project.
 
 Command :
 
-```unknown
+```bash
    mvn scm:status
 ```
 
@@ -176,7 +176,7 @@ tag
 
 `pom.xml` configuration :
 
-```unknown
+```xml
 <project>
   ...
   <build>
@@ -200,13 +200,13 @@ tag
 
 Command :
 
-```unknown
+```bash
    mvn scm:tag
 ```
 
 or you can specify the tag name in the command line
 
-```unknown
+```bash
    mvn -Dtag="<tag name>" scm:tag
 ```
 
@@ -215,7 +215,7 @@ unedit - unset the edit status of the project sources and 
unlocking it if suppor
 
 Command :
 
-```unknown
+```bash
    mvn scm:unedit
 ```
 
@@ -224,13 +224,13 @@ validate - check if the scm urls configured in the 
`pom.xml` is valid.
 
 Command :
 
-```unknown
+```bash
    mvn scm:validate
 ```
 
 or passing the scmConnection or/and the developerConnection in the command line
 
-```unknown
+```bash
    mvn -DscmConnection="<scm url>" -DscmDeveloperConnection="<scm url>" 
scm:validate
 ```
 
diff --git a/maven-scm-plugin/src/site/markdown/usage.md 
b/maven-scm-plugin/src/site/markdown/usage.md
index 17ad0265d..ea101d3e7 100644
--- a/maven-scm-plugin/src/site/markdown/usage.md
+++ b/maven-scm-plugin/src/site/markdown/usage.md
@@ -36,7 +36,7 @@ Each SCM has a different command line/library API invocation 
to commit the modif
 
 To configure the SCM support for Maven you need the 
[SCM](http://maven.apache.org/pom.html#SCM) configuration in your `pom.xml`.
 
-```unknown
+```xml
 <project>
   ...
   <packaging>jar</packaging>
@@ -54,7 +54,7 @@ To configure the SCM support for Maven you need the 
[SCM](http://maven.apache.or
 
 Maven will use the information embedded in the SCM configuration to determine 
the used SCM provider (implementation) and the remote repository URL. The SCM 
configuration URL is composed of different information that define the mapping:
 
-```unknown
+```text
    scm:svn:http://somerepository.com/svn_repo/trunk
    <service name>:<scm implementation>:<repository url>
 ```
@@ -67,13 +67,13 @@ Assuming that SCM has been configured in the `pom.xml` and 
the project directory
 
 **The files should be added beforehand by an external scm client.**
 
-```unknown
+```bash
   mvn -Dmessage="<commit_log_here>" scm:checkin
 ```
 
 for update
 
-```unknown
+```bash
   mvn scm:update
 ```
 
@@ -83,7 +83,7 @@ There two possible SCM connections that can be used in the 
`pom.xml`, connection
 
 - connection configuration
 
-    ```unknown
+    ```xml
     <project>
       ...
       <build>
@@ -107,7 +107,7 @@ There two possible SCM connections that can be used in the 
`pom.xml`, connection
 
 - developerConnection configuration
 
-    ```unknown
+    ```xml
     <project>
       ...
       <build>
diff --git a/src/site/markdown/guide/new_provider.md 
b/src/site/markdown/guide/new_provider.md
index 4e16b6089..d5b706fdf 100644
--- a/src/site/markdown/guide/new_provider.md
+++ b/src/site/markdown/guide/new_provider.md
@@ -43,7 +43,7 @@ In the next section, we&apos;ll see all the steps in details 
to write a new Mave
 
 Your project need to use some jars from the Maven SCM framework. Add them to 
your POM.
 
-```unknown
+```xml
 <project xmlns="http://maven.apache.org/POM/4.0.0"; 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; 
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 
http://maven.apache.org/xsd/maven-4.0.0.xsd";>
   <modelVersion>4.0.0</modelVersion>
 
@@ -85,7 +85,7 @@ The Sisu Maven Plugin will generate the components meta-data 
file used by the DI
 
 This class will contain all SCM information about your SCM connection (user, 
password, host, port, path...).
 
-```unknown
+```java
 package org.apache.maven.scm.provider.myprovider.repository;
 
 import org.apache.maven.scm.provider.ScmProviderRepository;
@@ -104,7 +104,7 @@ This class is the central point of the provider. The Maven 
SCM framework will kn
 
 Before you start to write your SCM provider, you must define the SCM URLs you 
want to support.
 
-```unknown
+```java
 package org.apache.maven.scm.provider.myprovider;
 
 import 
org.apache.maven.scm.provider.myprovider.repository.MyScmProviderRepository;
@@ -147,7 +147,7 @@ The JSR330 annotations will be used by the Sisu Maven 
Plugin, declared in the PO
 
 When you write a new SCM command, you must extend base classes for the Maven 
SCM framework. We have one base command for each command supported by Maven SCM 
and each command have an `execute` method that return an SCM result.
 
-```unknown
+```java
 package org.apache.maven.scm.provider.myprovider.command.checkout;
 
 import org.apache.maven.scm.command.checkout.AbstractCheckOutCommand;
@@ -172,7 +172,7 @@ public class MyCheckoutCommand
 
 Now that your command is implemented, you need to add it in your SCM provider 
(`MyScmProvider`). Open the provider class and override the method that relates 
to your command.
 
-```unknown
+```java
 public class MyScmProvider
     extends AbstractScmProvider
 {
diff --git a/src/site/markdown/guide/usage.md b/src/site/markdown/guide/usage.md
index 3045dc654..c46ec7986 100644
--- a/src/site/markdown/guide/usage.md
+++ b/src/site/markdown/guide/usage.md
@@ -31,7 +31,7 @@ under the License.
 
 With [Plexus](http://codehaus-plexus.github.io/), it&apos;s very easy to use 
Maven SCM because it injects all dependencies in fields, so you only have to 
write minimal code.
 
-```unknown
+```java
 import org.apache.maven.scm.manager.ScmManager;
 
 public class MyApp
@@ -57,7 +57,7 @@ public class MyApp
 
 Without Plexus, you must add all your SCM providers in the manager and that 
will require more work. You can use the basic SCM manager or write your own:
 
-```unknown
+```java
 import org.apache.maven.scm.manager.BasicScmManager;
 
 public class MyApp
@@ -84,7 +84,7 @@ public class MyApp
 
 Before you call a command, the SCM manager needs an `ScmRepository`. This 
object contains all the information about the SCM connection.
 
-```unknown
+```java
     public ScmRepository getScmRepository( String scmUrl )
         throw Exception
     {
@@ -107,7 +107,7 @@ Before you call a command, the SCM manager needs an 
`ScmRepository`. This object
 
 ### Checkout command
 
-```unknown
+```java
     public void checkOut( ScmRepository scmRepository, File workingDirectory )
         throws ScmException
     {
@@ -145,7 +145,7 @@ Before you call a command, the SCM manager needs an 
`ScmRepository`. This object
 
 ### Update command
 
-```unknown
+```java
     public void update( ScmRepository scmRepository, File workingDirectory )
         throws ScmException
     {
@@ -177,7 +177,7 @@ Before you call a command, the SCM manager needs an 
`ScmRepository`. This object
 
 In each sample command code, we use the `checkResult` method, it isn&apos;t 
required but can be useful if something failed in the command execution.
 
-```unknown
+```java
     public void checkResult( ScmResult result )
         throws Exception
     {

Reply via email to