it looks like the assumption the author was making is incorrect; the commit message was "Use the execution from the maven super pom for source plugin", but the super pom should not come into play because:
The maven-source-plugin is only defined to be executed by the Super POM when the release-profile profile is active.
The release-profile profile is deprecated.
so, the commit author was either wrong, or this was intentionally and nefariously designed to stop source JAR generation a few versions before FR cut off access to the trunk, to curtail how many copies are floating out there.
the linked ticket is AME-9491, but that's only accessible by FR Backstage customers with a subscription. with access to the ticket we can't confirm motivation behind the change.
looks like FR stopped including the
<executions>tag for themaven-source-pluginstarting in version 2.0.6 offorgerock-parent. the commit that made this change was https://github.com/WrenSecurity/wrensec-parent/commit/268d9fce942e75539b40041033e6173ca998bd9f.it looks like the assumption the author was making is incorrect; the commit message was "Use the execution from the maven super pom for source plugin", but the super pom should not come into play because:
maven-source-pluginis only defined to be executed by the Super POM when therelease-profileprofile is active.release-profileprofile is deprecated.so, the commit author was either wrong, or this was intentionally and nefariously designed to stop source JAR generation a few versions before FR cut off access to the trunk, to curtail how many copies are floating out there.
the linked ticket is AME-9491, but that's only accessible by FR Backstage customers with a subscription. with access to the ticket we can't confirm motivation behind the change.