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-invoker-plugin.git
The following commit(s) were added to refs/heads/master by this push:
new e4ab4f6 Give code blocks a real language instead of unknown
e4ab4f6 is described below
commit e4ab4f60241ecf0fdb55be3525747ec373b505ef
Author: Sylwester Lachiewicz <[email protected]>
AuthorDate: Sun Nov 1 15:18:03 2026 +0000
Give code blocks a real language instead of unknown
---
src/site/markdown/examples/filtering.md.vm | 2 +-
src/site/markdown/examples/invoker-properties.md | 2 +-
src/site/markdown/examples/pre-post-build-script.md.vm | 6 +++---
src/site/markdown/examples/selector-scripts.md.vm | 2 +-
src/site/markdown/usage.md.vm | 2 +-
5 files changed, 7 insertions(+), 7 deletions(-)
diff --git a/src/site/markdown/examples/filtering.md.vm
b/src/site/markdown/examples/filtering.md.vm
index eb45540..2050569 100644
--- a/src/site/markdown/examples/filtering.md.vm
+++ b/src/site/markdown/examples/filtering.md.vm
@@ -29,7 +29,7 @@ Some files of the sub projects can be filtered, i.e. special
tokens will be repl
The following example directory structure highlights the files which are
filtered by the Invoker Plugin:
-```unknown
+```text
./
+- pom.xml
+- src/
diff --git a/src/site/markdown/examples/invoker-properties.md
b/src/site/markdown/examples/invoker-properties.md
index d537e88..72b43c2 100644
--- a/src/site/markdown/examples/invoker-properties.md
+++ b/src/site/markdown/examples/invoker-properties.md
@@ -21,7 +21,7 @@ under the License.
The various parameters in the plugin configuration provide a means to globally
configure the goals, profiles etc. used to run a Maven build on the projects.
However, for certain projects you might want to specify different settings. To
avoid the hassle of multiple plugin executions, you can simply use a file named
`invoker.properties` to control the build settings on a per project basis or in
one of its ancestor folders to apply it for a group of projects. The exact name
of this properti [...]
-```unknown
+```text
./
+- src/
+- it/
diff --git a/src/site/markdown/examples/pre-post-build-script.md.vm
b/src/site/markdown/examples/pre-post-build-script.md.vm
index ee27e00..e26b575 100644
--- a/src/site/markdown/examples/pre-post-build-script.md.vm
+++ b/src/site/markdown/examples/pre-post-build-script.md.vm
@@ -31,7 +31,7 @@ You can also define a user properties which will be added to
executed test proje
Here is an example of groovy script:
-```unknown
+```groovy
def userProperties = context.get('userProperties')
def server = new MockServer()
@@ -96,14 +96,14 @@ Below is an example post-build Groovy script
(`verify.groovy`) that checks for t
Example `verify.groovy`
-```unknown
+```groovy
def file = new File( basedir, "target/my-test-project-1.0-SNAPSHOT.jar" )
assert file.isFile()
```
The same check as a deprecated BeanShell script (`verify.bsh`), for existing
scripts that have not been ported yet:
-```unknown
+```java
import java.io.*;
File file = new File( basedir, "target/my-test-project-1.0-SNAPSHOT.jar" );
diff --git a/src/site/markdown/examples/selector-scripts.md.vm
b/src/site/markdown/examples/selector-scripts.md.vm
index c46c23a..6d47ade 100644
--- a/src/site/markdown/examples/selector-scripts.md.vm
+++ b/src/site/markdown/examples/selector-scripts.md.vm
@@ -21,7 +21,7 @@ under the License.
Starting with plugin version 1.5, a custom script can be used to skip
individual projects based on whatever criteria expressed in the script as
illustrated in the following example. Write the script in Groovy; BeanShell
scripts are deprecated and the plugin warns when it runs one. Assume the
following directory structure:
-```unknown
+```text
./
+- pom.xml
+- src/
diff --git a/src/site/markdown/usage.md.vm b/src/site/markdown/usage.md.vm
index 109d1ea..7837e31 100644
--- a/src/site/markdown/usage.md.vm
+++ b/src/site/markdown/usage.md.vm
@@ -26,7 +26,7 @@ Basic Example
The following example demonstrates a basic plugin configuration for running
integration tests. Let's assume the following directory structure of your
project:
-```unknown
+```text
./
+- pom.xml
+- src/