This is an automated email from the ASF dual-hosted git repository.
slachiewicz pushed a commit to branch maven-install-plugin-4.x
in repository https://gitbox.apache.org/repos/asf/maven-install-plugin.git
The following commit(s) were added to refs/heads/maven-install-plugin-4.x by
this push:
new f2be464 Give code blocks a real language instead of unknown
f2be464 is described below
commit f2be4640396a71d538bb186b9f51aa332ddba77d
Author: Sylwester Lachiewicz <[email protected]>
AuthorDate: Mon Nov 2 14:11:03 2026 +0000
Give code blocks a real language instead of unknown
---
src/site/markdown/examples/custom-pom-installation.md.vm | 4 ++--
src/site/markdown/examples/generic-pom-generation.md.vm | 2 +-
src/site/markdown/examples/installing-secondary-artifacts.md.vm | 2 +-
src/site/markdown/examples/specific-local-repo.md.vm | 2 +-
src/site/markdown/usage.md | 4 ++--
5 files changed, 7 insertions(+), 7 deletions(-)
diff --git a/src/site/markdown/examples/custom-pom-installation.md.vm
b/src/site/markdown/examples/custom-pom-installation.md.vm
index 5c10b8c..52aaa3b 100644
--- a/src/site/markdown/examples/custom-pom-installation.md.vm
+++ b/src/site/markdown/examples/custom-pom-installation.md.vm
@@ -28,13 +28,13 @@ under the License.
The Apache Maven Install Plugin can include a pre-built custom POM with the
artifact in the local repository. Just set the value of the `pomFile` parameter
to the path of the custom POM.
-```unknown
+```shell
mvn ${project.groupId}:${project.artifactId}:${project.version}:install-file
-Dfile=path-to-your-artifact-jar -DpomFile=path-to-pom
```
If the JAR was built by Apache Maven, it'll contain a pom.xml in a subfolder
of the META-INF directory, which will be read by default. In that case, all you
need to do is:
-```unknown
+```shell
mvn ${project.groupId}:${project.artifactId}:${project.version}:install-file
-Dfile=<path-to-file>
```
diff --git a/src/site/markdown/examples/generic-pom-generation.md.vm
b/src/site/markdown/examples/generic-pom-generation.md.vm
index 44224ea..6feae06 100644
--- a/src/site/markdown/examples/generic-pom-generation.md.vm
+++ b/src/site/markdown/examples/generic-pom-generation.md.vm
@@ -28,7 +28,7 @@ under the License.
There are times when you do not have a POM for a 3rd party artifact. For
instance, when installing a proprietary or commercial JAR into a repository.
The Install Plugin can create a generic POM in this case which contains the
minimal set of POM elements required by Maven, such as groupId, artifactId,
version, packaging. You tell Maven to generate a POM by setting the
`generatePom` parameter to `true`.
-```unknown
+```shell
mvn ${project.groupId}:${project.artifactId}:${project.version}:install-file
-Dfile=path-to-your-artifact-jar \
-DgroupId=your.groupId \
-DartifactId=your-artifactId \
diff --git a/src/site/markdown/examples/installing-secondary-artifacts.md.vm
b/src/site/markdown/examples/installing-secondary-artifacts.md.vm
index 46f0466..659bf29 100644
--- a/src/site/markdown/examples/installing-secondary-artifacts.md.vm
+++ b/src/site/markdown/examples/installing-secondary-artifacts.md.vm
@@ -30,7 +30,7 @@ Sometimes you need to install secondary artifacts after the
main artifact has be
Let us assume that you want to install the sources for an old artifact, like
commons-logging-1.0.3. The [central
repository](http://repo1.maven.org/maven2/commons-logging/commons-logging/1.0.3/)
only has the main artifact and a `-javadoc` artifact for that version. Package
up the sources into a JAR file on your local disk and then run the following
command:
-```unknown
+```shell
mvn ${project.groupId}:${project.artifactId}:${project.version}:install-file
-Dfile=path-to-commons-logging-sources.jar \
-DgroupId=commons-logging \
-DartifactId=commons-logging \
diff --git a/src/site/markdown/examples/specific-local-repo.md.vm
b/src/site/markdown/examples/specific-local-repo.md.vm
index 0a9ae7c..c7c5a5e 100644
--- a/src/site/markdown/examples/specific-local-repo.md.vm
+++ b/src/site/markdown/examples/specific-local-repo.md.vm
@@ -33,7 +33,7 @@ By default, the Apache Maven Install Plugin uses the local
repository defined in
You could install an artifact on a specific local repository by setting the
`localRepositoryPath` parameter when installing.
-```unknown
+```shell
mvn ${project.groupId}:${project.artifactId}:${project.version}:install-file
-Dfile=path-to-your-artifact-jar \
-DgroupId=your.groupId \
-DartifactId=your-artifactId \
diff --git a/src/site/markdown/usage.md b/src/site/markdown/usage.md
index 36b47cc..51ce693 100644
--- a/src/site/markdown/usage.md
+++ b/src/site/markdown/usage.md
@@ -35,7 +35,7 @@ With the `maven-install-plugin` you can put your artifacts in
the local reposito
In most cases, `install:install` goal doesn't need any configuration, it needs
the project's POM and the artifact file to be installed during the `install`
phase of the default build lifecycle.
-```unknown
+```shell
mvn install
```
@@ -43,7 +43,7 @@ mvn install
The `install:install-file` goal is used primarily for installing artifacts to
the local repository which were not built by Maven. The project's development
team may or may not provide a POM for the artifact. Here's a list of some of
the available parameters for the `install-file` goal:
-```unknown
+```shell
mvn install:install-file -Dfile=your-artifact-1.0.jar \
[-DpomFile=your-pom.xml] \
[-Dsources=src.jar] \