I would like to upload, deploy an existing jar to artifactory.

There is a pipeline from a third party, I have no control over whatsoever, which step 1 will build a jar. The jar is then put on a host, in its file directory. Again, I have no control over the job itself.

But I can see when manually getting into the host that the jar is correct by doing jar xf thejar.jar. The extracted content would have all the proper class files.

Now, my part, step 2, I am trying to upload this jar into an artifactory.

I understand there is an option to run mvn deploy, but this would run all the previous steps of the maven life cycle. Since the jar is correct, I would like to avoid this duplication (running all the previous step of the maven life cycle) and just upload the jar.

I came across 2 solutions so far:

1. run mvn deploy:deploy it seems this solution does not rerun everything, but just try to upload the jar

2. run mvn jar:jar deploy:deploy same, it seems this solution does not rerun everything, but just try to upload the jar

However, solution 1 would yield the following issue:

[INFO] ----------------------< com.example:mavendeploy >-----------------------
[INFO] Building mavendeploy 4.3
[INFO]   from pom.xml
[INFO] --------------------------------[ jar ]---------------------------------
[INFO] 
[INFO] --- deploy:3.1.2:deploy (default-cli) @ mavendeploy ---
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  0.329 s
[INFO] Finished at: 2025-T19:26:20Z
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal .apache.maven.plugins:maven-deploy-plugin:3.1.2:deploy (default-cli) on project mavendeploy: The packaging plugin for project mavendeploy did not assign a file to the build artifact -> [Help 1]

It looks like it does not even detect the jar.

While the second solution will yield this issue.

[INFO] --------------------------------[ jar ]---------------------------------
[INFO] 
[INFO] --- jar:3.4.1:jar (default-cli) @ mavendeploy ---
[WARNING] JAR will be empty - no content was marked for inclusion!
[INFO] Building jar: /builds/path/to/jar/mavendeploy-4.3.jar
[INFO] 
[INFO] --- deploy:3.1.2:deploy (default-cli) @ mavendeploy ---
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------

While it seems to detect the correct jar properly, there is this warning, JAR will be empty and also, while the jar seems to be indeed uploaded to artifactory, the jar downloaded from the artifactory does not contain any of the classes files. Why?

What is the proper way to upload an existing jar into artifactory using mvn deploy (hopefully without having to rerun the whole maven lifecycle, since the jar is already there)?

What did I do wrong in solution 1 or solution 2?

I would like to upload, deploy an existing jar to artifactory.

There is a pipeline from a third party, I have no control over whatsoever, which step 1 will build a jar. The jar is then put on a host, in its file directory. Again, I have no control over the job itself.

But I can see when manually getting into the host that the jar is correct by doing jar xf thejar.jar. The extracted content would have all the proper class files.

Now, my part, step 2, I am trying to upload this jar into an artifactory.

I understand there is an option to run mvn deploy, but this would run all the previous steps of the maven life cycle. Since the jar is correct, I would like to avoid this duplication (running all the previous step of the maven life cycle) and just upload the jar.

I came across 2 solutions so far:

1. run mvn deploy:deploy it seems this solution does not rerun everything, but just try to upload the jar

2. run mvn jar:jar deploy:deploy same, it seems this solution does not rerun everything, but just try to upload the jar

However, solution 1 would yield the following issue:

[INFO] ----------------------< com.example:mavendeploy >-----------------------
[INFO] Building mavendeploy 4.3
[INFO]   from pom.xml
[INFO] --------------------------------[ jar ]---------------------------------
[INFO] 
[INFO] --- deploy:3.1.2:deploy (default-cli) @ mavendeploy ---
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  0.329 s
[INFO] Finished at: 2025-T19:26:20Z
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal .apache.maven.plugins:maven-deploy-plugin:3.1.2:deploy (default-cli) on project mavendeploy: The packaging plugin for project mavendeploy did not assign a file to the build artifact -> [Help 1]

It looks like it does not even detect the jar.

While the second solution will yield this issue.

[INFO] --------------------------------[ jar ]---------------------------------
[INFO] 
[INFO] --- jar:3.4.1:jar (default-cli) @ mavendeploy ---
[WARNING] JAR will be empty - no content was marked for inclusion!
[INFO] Building jar: /builds/path/to/jar/mavendeploy-4.3.jar
[INFO] 
[INFO] --- deploy:3.1.2:deploy (default-cli) @ mavendeploy ---
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------

While it seems to detect the correct jar properly, there is this warning, JAR will be empty and also, while the jar seems to be indeed uploaded to artifactory, the jar downloaded from the artifactory does not contain any of the classes files. Why?

What is the proper way to upload an existing jar into artifactory using mvn deploy (hopefully without having to rerun the whole maven lifecycle, since the jar is already there)?

What did I do wrong in solution 1 or solution 2?

• java
• maven
• jar

1 Answer 1

To upload an existing artifact, you need to use deploy:deploy-file

See also https://maven.apache./plugins/maven-deploy-plugin/deploy-file-mojo.html