arturobernalg opened a new pull request, #369:
URL: https://github.com/apache/maven-source-plugin/pull/369

   AggregatorSourceJarMojo packaged sources from reactorProjects, the full list 
of every project in the current build, rather than just this project's own 
descendants. Binding the aggregate goal in two sibling aggregator POMs (e.g. a 
client and a server subtree under a common parent) made each one's sources jar 
pull in the other's sources whenever both were built together as part of the 
larger reactor, even though neither is a module of the other.
   
   Use getCollectedProjects() instead, which is exactly this project's own 
module tree regardless of what else is in the reactor, so the resulting archive 
no longer depends on how the build was invoked.
   
   Added IT MSOURCES-115: a three-level reactor (parent, two aggregator 
siblings, one leaf module under each) building the whole tree, and checking 
each sibling's sources jar contains only its own leaf's source and not the 
other sibling's.
   
   
   
   
   To make clear that you license your contribution under
   the [Apache License Version 2.0, January 
2004](https://www.apache.org/licenses/LICENSE-2.0)
   check one of the following:
   
   - [x] I hereby declare this contribution to be licensed under the [Apache 
License Version 2.0, January 2004](https://www.apache.org/licenses/LICENSE-2.0)
   - [x] I hereby declare that I have filed an [Apache Individual Contributor 
License Agreement](https://www.apache.org/licenses/icla.pdf).
   


-- 
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]

Reply via email to