jira-importer commented on issue #205: URL: https://github.com/apache/maven-source-plugin/issues/205#issuecomment-2959556878
**[Rob Vesse](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=rvesse)** commented Put together a minimal reproducer and did some analysis at https://github.com/rvesse/source-plugin-breaks-releases For my particular case it's the interaction between this new duplicate invocation check and the implicit release profile that the `maven-release-plugin` activates by default (at least for their 2.x versions). You can get Maven to show you the pom with the excess invocation by activating the implicit release profile via the `performRelease` property as the release plugin does i.e. `mvn help:effective-pom -DperformRelease=true` I was using the `jar` goal of the `maven-source-plugin` in my own `pom.xml` and the implicit release profile adds an additional `jar-no-fork` goal hence failing the duplicate invocation check. One workaround I found was to disable usage of the implicit release profile, this can most easily done by upgrading to a 3.x release of the `maven-release-plugin` as they now disable usage of that by default. Or if you need to continue using a 2.x version of the release plugin you can add `<useReleaseProfile>false</useReleaseProfile>` to the plugin configuration. -- 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]
