jira-importer opened a new issue, #400: URL: https://github.com/apache/maven-deploy-plugin/issues/400
**[Victoria](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=tory)** opened **[MDEPLOY-288](https://issues.apache.org/jira/browse/MDEPLOY-288?redirect=false)** and commented We have a project without primary artifact. Previously, we were using _maven-deploy-plugin:2.7_ and everything worked as expected: attached artifacts were deployed instead. Works the same way with version _2.8.2_. > `[16:58:57] : [Step 2/2] [INFO] — maven-deploy-plugin:2.7:deploy (default-deploy) @ project-without-primary-artifact ---` > > `[16:58:57] : [Step 2/2] [INFO] No primary artifact to deploy, deploying attached artifacts instead.` > > `[16:58:57] : [Step 2/2] Uploading: https://<repo>/project-without-primary-artifact/1.0-v5/project-without-primary-artifact-1.0-v5.pom` > > `[16:58:57] : [Step 2/2] Uploaded: https://<repo>/project-without-primary-artifact/1.0-v5/project-without-primary-artifact-1.0-v5.pom (12 KB at 21.0 KB/sec)` > > `[16:58:58] : [Step 2/2] Uploading: https://<repo>/project-without-primary-artifact/maven-metadata.xml` > > `[16:58:59] : [Step 2/2] Uploaded: https://<repo>/project-without-primary-artifact/maven-metadata.xml (2 KB at 4.8 KB/sec)` > > `[16:58:59] : [Step 2/2] Uploading: https://<repo>/project-without-primary-artifact/1.0-v5/project-without-primary-artifact-1.0-v5.zip` > > `[16:58:59] : [Step 2/2] Uploaded: https://<repo>/project-without-primary-artifact/1.0-v5/project-without-primary-artifact-1.0-v5.zip (42 KB at 67.3 KB/sec)` > > `[16:58:59] : [Step 2/2] [INFO] ------------------------------------------------------------------------` > > `[16:58:59] : [Step 2/2] [INFO] BUILD SUCCESS` > > `[16:58:59] : [Step 2/2] [INFO] ------------------------------------------------------------------------` > > `[16:58:59] : [Step 2/2] [INFO] Total time: 30.067s` > > `[16:58:59] : [Step 2/2] [INFO] Finished at: Tue Feb 25 16:58:59 UTC 2020` > > `[16:59:00] : [Step 2/2] [INFO] Final Memory: 68M/724M` > > `[16:59:00] : [Step 2/2] [INFO] ------------------------------------------------------------------------` > > `[16:59:00] : [Step 2/2] Process exited with code 0` However, after upgrading to _maven-deploy-plugin:3.0.0-M1_ the same build fails: > `[15:44:53] : [Step 2/2] [INFO] — maven-deploy-plugin:3.0.0-M1:deploy (default-deploy) @ project-without-primary-artifact ---` > > `[15:44:53]E: [Step 2/2] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:3.0.0-M1:deploy (default-deploy) on project project-without-primary-artifact: NoFileAssignedException` > > `[15:44:53] : [Step 2/2] [INFO] ------------------------------------------------------------------------` > > `[15:44:53] : [Step 2/2] [INFO] BUILD FAILURE` > > `[15:44:53] : [Step 2/2] [INFO] ------------------------------------------------------------------------` > > `[15:44:53] : [Step 2/2] [INFO] Total time: 26.250 s` > > `[15:44:53] : [Step 2/2] [INFO] Finished at: 2021-10-08T15:44:53+00:00` > > `[15:44:54] : [Step 2/2] [INFO] Final Memory: 78M/921M``[15:44:54] : [Step 2/2] [INFO] ------------------------------------------------------------------------` > > `[15:44:54]W: [Step 2/2] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:3.0.0-M1:deploy (default-deploy) on project project-without-primary-artifact: NoFileAssignedException: The packaging plugin for this project did not assign a main file to the project but it has attachments. Change packaging to 'pom'. -> [Help 1]` > Similar issue appears in _maven-install-plugin:3.0.0-M1_: https://issues.apache.org/jira/browse/MINSTALL-151 --- **Affects:** 3.0.0-M1 **Issue Links:** - [MDEPLOY-205](https://issues.apache.org/jira/browse/MDEPLOY-205) MavenProject with only attachments must have packaging "pom" (_**"is caused by"**_) - [MINSTALL-151](https://issues.apache.org/jira/browse/MINSTALL-151) Projects without primary artifacts, but with attachment artifacts fail install -- 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.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
