jira-importer commented on issue #205: URL: https://github.com/apache/maven-source-plugin/issues/205#issuecomment-2959556835
**[Rob Vesse](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=rvesse)** commented I don't understand the lack of urgency from the Maven Source Plugin developers here. You've got lots of examples here, and on related issues such as MSOURCES-140 where this change in your plugins behaviour is breaking peoples longstanding build processes. I've got a whole bunch of projects, some with parent POMs, some completely standalone, where upgrading to 3.3.0 breaks the ability to do a Maven release, and most frustratingly not until the `release:perform` stage forcing a `release:rollback`. I've spent far too much time staring at `mvn help:effective-pom` output to try to understand why/how I'm invoking the source plugin multiple times because as far as I can see I am not yet I hit the error unless I rollback to 3.2.1 -- 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
