This is an automated email from the ASF dual-hosted git repository.
elharo pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/maven-site.git
The following commit(s) were added to refs/heads/master by this push:
new ee43a82a grammar (#1474)
ee43a82a is described below
commit ee43a82a6ad97c640b40a3f787c0006e3720b6e8
Author: Elliotte Rusty Harold <[email protected]>
AuthorDate: Thu Dec 4 13:25:58 2025 +0000
grammar (#1474)
---
content/markdown/guides/mini/guide-3rd-party-jars-remote.md | 11 +++++++----
1 file changed, 7 insertions(+), 4 deletions(-)
diff --git a/content/markdown/guides/mini/guide-3rd-party-jars-remote.md
b/content/markdown/guides/mini/guide-3rd-party-jars-remote.md
index 793e141a..c6d45534 100644
--- a/content/markdown/guides/mini/guide-3rd-party-jars-remote.md
+++ b/content/markdown/guides/mini/guide-3rd-party-jars-remote.md
@@ -19,9 +19,9 @@ under the License.
# Guide to deploying 3rd party JARs to remote repository
-Same concept of the [install:install-file](./guide-3rd-party-jars-local.html)
goal of the maven-install-plugin where the 3rd party JAR is installed in the
local repository. But this time instead to local repository the JAR will be
install both in the local and remote repository.
+Same concept of the [install:install-file](./guide-3rd-party-jars-local.html)
goal of the maven-install-plugin where the 3rd party JAR is installed in the
local repository. But this time the JAR will be installed both in the local and
remote repository.
-To deploy a 3rd party JAR use the deploy:deploy-file goal under
maven-deploy-plugin.
+To deploy a 3rd party JAR, use the deploy:deploy-file goal under
maven-deploy-plugin.
First, the wagon-provider(wagon-ftp, wagon-file, etc..) must be placed to your
`${maven.home}/lib`.
@@ -39,7 +39,7 @@ mvn deploy:deploy-file -DgroupId=<group-id> \
## Deploying a 3rd party JAR with a generic POM
-By default, deploy:deploy-file generates a generic POM(.pom) to be deploy
together with the 3rd party JAR. To disable this feature we should set the
`generatePOM` argument to false.
+By default, deploy:deploy-file generates a generic POM(.pom) to be deployed
together with the 3rd party JAR. To disable this feature we should set the
`generatePOM` argument to false.
```
-DgeneratePom=false
@@ -47,7 +47,8 @@ By default, deploy:deploy-file generates a generic POM(.pom)
to be deploy togeth
## Deploying a 3rd party JAR with a customized POM
-If a POM is already existing for the 3rd Party JAR and you want to deploy it
together with the JAR we should use the `pomFile` argument of the deploy-file
goal. See sample below.
+If a POM already exists for the third party JAR and you want to deploy it
together with the JAR,
+you should use the `pomFile` argument of the deploy-file goal. See sample
below.
```
mvn deploy:deploy-file -DpomFile=<path-to-pom> \
@@ -60,5 +61,7 @@ Note that `groupId`, `artifactId`, `version` and `packaging`
arguments are not i
## Deploying Source Jars
+<!-- TODO: Check the following, cause i don't this is true anymore. I assume
packaging should be jar-->
+<!-- and the classifier should be set to source.-->
To deploy a 3rd party source jar, packaging should be set to `java-source`,
and generatePom should be set to `false`.
