jira-importer commented on issue #313: URL: https://github.com/apache/maven-install-plugin/issues/313#issuecomment-2771867400
**[Guillermo Fernandes](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=gsfernandes)** commented I would say that makes sense to break if the plugin defines a packaging and it not setting the main artifact but... it was working before for a long time... So, I would either prefer a warning message instead of this exception and let the whole community know that this will be changed from a warning message to an error in 3.0.0 version. The thing here is that suddenly we have seen this issue in customer environments as well in our environments when installing artifacts that use our maven plugin (which defines the custom packaging and is not setting the main artifact) as we were not setting a fixed version of maven-install-plugin as soon as 3.0.0-M1 was deployed they started to use this version and got this issue. Would it make sense as even this is a milestone version to log a warning and once 3.0.0 is released just throw the error? I'm wondering how many custom maven plugins may have this issue too. -- 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
