jira-importer commented on issue #408: URL: https://github.com/apache/maven-deploy-plugin/issues/408#issuecomment-2771538290
**[Michaël](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=JIRAUSER305673)** commented The root cause of this issue is discussed in https://issues.apache.org/jira/browse/MNG-8138 TLDR; invoking the jar:jar task directly changes the (internal) state of a pom project/module to think it has a jar to deploy. The deploy plugin consequently tries to honor that and that is the behaviour you are observing. The "best" way of solving this is not invoking the tasks directly but using the maven lifecycles and configuring your project accordingly. A shortcut worth trying is to mark skip the maven-jar-plugin for the pom module (mentioned in above ticket) `<plugin> {color`} ` <groupId>org.apache.maven.plugins</groupId> {color`} ` <artifactId>maven-jar-plugin</artifactId>{color`} ` <configuration> <skipIfEmpty>true</skipIfEmpty> </configuration>{color`} `</plugin>` -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
