[
https://issues.apache.org/jira/browse/HBASE-16318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15425562#comment-15425562
]
Hudson commented on HBASE-16318:
--------------------------------
FAILURE: Integrated in Jenkins build HBase-1.3-IT #792 (See
[https://builds.apache.org/job/HBase-1.3-IT/792/])
HBASE-16318 consistently use the correct name for 'Apache License, (busbey: rev
75950de09ea9b0f1dc893f0724c73fb2a618e4ed)
* (edit) hbase-resource-bundle/src/main/resources/META-INF/LICENSE.vm
* (edit) hbase-resource-bundle/src/main/resources/supplemental-models.xml
* (edit) pom.xml
HBASE-16318 fail build while rendering velocity template if dependency (busbey:
rev 4e78f7a99e4d3fd264fb64446b52bf082b4ee6e6)
* (edit) hbase-resource-bundle/src/main/resources/META-INF/LICENSE.vm
> fail build if license isn't in whitelist
> ----------------------------------------
>
> Key: HBASE-16318
> URL: https://issues.apache.org/jira/browse/HBASE-16318
> Project: HBase
> Issue Type: Sub-task
> Components: build, dependencies
> Reporter: Sean Busbey
> Assignee: Sean Busbey
> Fix For: 2.0.0, 1.3.0, 1.4.0, 1.2.3, 0.98.22, 1.1.7
>
> Attachments: HBASE-16318.0.patch, HBASE-16318.1.patch,
> HBASE-16318.2.patch, HBASE-16318.3.patch
>
>
> we use supplemental-models.xml to make sure we have consistent names and
> descriptions for licenses. we also know what licenses we expect to see in our
> build. If we see a different one
> # fail the velocity template process
> # if possible, include some information about why this happened
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
