[
https://issues.apache.org/jira/browse/PIO-27?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15461854#comment-15461854
]
Andrew Purtell commented on PIO-27:
-----------------------------------
For the reason Pat mentioned (figuring out what binary deps is harder than
source) if I recall correctly the guidelines require the binary LICENSE and
NOTICE files to be included in each released PIO binary jar. We did a fair
amount of maven hacking over on HBase to programmatically aggregate all LICENSE
and NOTICE files of our dependencies into one for our binaries and the place
that aggregation into each of our binary jars. Don't know how to do that with
SBT. I think you can get there, but source only to start will be simpler and
faster to manage.
> Check release artifacts for licenses and the LICENSE.txt file
> -------------------------------------------------------------
>
> Key: PIO-27
> URL: https://issues.apache.org/jira/browse/PIO-27
> Project: PredictionIO
> Issue Type: Task
> Affects Versions: 0.10.0
> Reporter: Pat Ferrel
> Priority: Blocker
> Fix For: 0.10.0
>
>
> Quoth [~smarthi] " I would ask that you do the due diligence on the
> License and Notice files and ensure that all third party jars have been
> accounted for and the License and Notice files are included in the
> appropriate project release artifacts."
> This has to be done by hand. We should be able to do it now on the develop
> branch build since we will not include new features and so no new
> dependencies.
> https://github.com/apache/incubator-predictionio/blob/develop/LICENSE.txt
> https://github.com/apache/incubator-predictionio/blob/develop/NOTICE.txt
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
