jira-importer commented on issue #313: URL: https://github.com/apache/maven-install-plugin/issues/313#issuecomment-2771867367
**[Guillermo Fernandes](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=gsfernandes)** commented Hi [Karl Heinz Marbaise](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=khmarbaise), We are having the same issue, seems that 3.0.0-M1 has changed its behaviour when installing a project without main artifact but with attachments. maven-installer-plugin 2.5.2 was just logging an info message on this scenario: https://github.com/apache/maven-install-plugin/blob/maven-install-plugin-2.5.2/src/main/java/org/apache/maven/plugin/install/InstallMojo.java#L203 ```java getLog().info( "No primary artifact to install, installing attached artifacts instead." ); ``` 3.0.0-M1 instead delegates this logic to maven-artifact-transfer which throws an exception on this case: https://github.com/apache/maven-artifact-transfer/blob/maven-artifact-transfer-0.10.0/src/main/java/org/apache/maven/shared/transfer/project/install/internal/DefaultProjectInstaller.java#L116 I know that would make sense to fail on this scenarios but I'm wondering if this intentional or just you were not aware that this will break builds where plugins declare a custom packaging and are not setting the main artifact to the project. Regards, -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
