Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/125#issuecomment-37441481
Right now we manually run RAT before making releases - but the proposal
here was to run it every time a PR is created. That will be much better since
we will catch license issues earlier on and they won't delay releases.
Since the Maven RAT plug-in is only a thin wrapper on just running rat
manually, my proposal was for now we just run it directly on the source code.
That way it is build agnostic.
All that said - @ScrapCodes - embedding RAT inside of Spark has some
issues. It would make more sense to use the same thing we use for sbt which is,
try to download the RAT jar from maven if it's not already downloaded. Then we
just have to have a very small script in the build instead of bundling all of
RAT. This is identical to the situation with the sbt jar. Like @aarondav
suggested.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
