jira-importer commented on issue #205: URL: https://github.com/apache/maven-source-plugin/issues/205#issuecomment-2959556842
**[Romain Manni-Bucau](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=romain.manni-bucau)** commented [Rob Vesse](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=rvesse) probably linked to the fact the bug is not on maven plugin side but the project setup, if you look your build output you will see multiple executions attaching the same binary for sources which was a bug in earlier versions, using it is no more supported (for goods) but can break builds which were abusing this bug. You can see it earlier binding source plugin to an earlier stage - this is mainly dependent your project setup. So while I understand it is bothering it also show you have a bug in your maven usage so it is good. Side note: you'll get the same kind of validation with maven 4 upgrade which will start to fail with missing enabled profiles instead of ignoring it and all that for a better usage and enforce the control of the build instead of faking build was fine when it was not. -- 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]
