[
https://issues.apache.org/jira/browse/MSOURCES-115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17959488#comment-17959488
]
Matthias Bünger commented on MSOURCES-115:
------------------------------------------
This project has moved from Jira to GitHub Issues. This issue was migrated to
[apache/maven-source-plugin#185|https://github.com/apache/maven-source-plugin/issues/185].
Please visit the GitHub issue to view further activity, add comments, or
subscribe to receive notifications.
> aggregate-sources yields different results based on reactor
> -----------------------------------------------------------
>
> Key: MSOURCES-115
> URL: https://issues.apache.org/jira/browse/MSOURCES-115
> Project: Maven Source Plugin (Moved to GitHub Issues)
> Issue Type: Bug
> Affects Versions: 3.0.1
> Reporter: Raymond DeCampo
> Priority: Major
>
> The main idea here is that depending on whether a particular project is built
> from the parent project or on its own, the sources jar generated by
> aggregate-sources may be different. IMO this attacks the repeat-ability of
> the build. The root cause is that aggregate-sources pulls in all the sources
> in the reactor.
>
> Consider a three layer structure. One parent project at the top level, say
> foo-parent. Then two child modules at the next level, say foo-client and
> foo-server. Then some number of children of foo-client and foo-server where
> the actual Java code lives.
>
> The poms for foo-server and foo-client have aggregate-sources set up. If a
> build is executed directly on foo-client for example, then the resulting
> source foo-client-sources-*.jar will have the source from the children of
> foo-client.
>
> If a build is executed from foo-parent, both foo-client and foo-server are
> included in the reactor. Now the resulting foo-client-sources-*.jar includes
> the source code from foo-server's children as well as its own.
>
> I would expect that the aggregate-sources target would only include the
> source of the children of the current project instead of the source from any
> project in the reactor. I would also expect that the build should result
> identical artifacts whether or not it is invoked from the parent project or
> not.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
