[jira] [Created] (HAWQ-327) Clover License Violation

["Goden Yao (JIRA)" <ji...@apache.org>]

Goden Yao created HAWQ-327:
------------------------------

             Summary: Clover License Violation
                 Key: HAWQ-327
                 URL: https://issues.apache.org/jira/browse/HAWQ-327
             Project: Apache HAWQ
          Issue Type: Task
          Components: Build, Tests
            Reporter: Goden Yao
            Assignee: Jiali Yao


   ./contrib/hawq-hadoop/lib/clover.license

Thanks to [~cwelton]'s investigation:
{quote}
This looks like it is the code coverage tool that was used for the
hawq-hadoop contrib module, the license file is referenced by all the pom
files under contrib/hawq-hadoop and I expect it would break at least the
code coverage tests if it was removed.

./hawq-mapreduce-ao/pom.xml:
 <licenseLocation>../lib/clover.license</licenseLocation>
./hawq-mapreduce-common/pom.xml:
 <licenseLocation>../lib/clover.license</licenseLocation>
./hawq-mapreduce-parquet/pom.xml:
 <licenseLocation>../lib/clover.license</licenseLocation>
./hawq-mapreduce-tool/pom.xml:
 <licenseLocation>../lib/clover.license</licenseLocation>
./pom.xml: <licenseLocation>lib/clover.license</licenseLocation>

That said... I strongly doubt that it is kosher to place a license file
that almost certainly was not a worldwide license into the OSS. This should
be removed and Pivotal should contact Atlassian about the unintentional
license leak.

For reference this[1] looks like the correct identity resolution for this
particular 'clover'.

[1] https://confluence.atlassian.com/display/CLOVER/About+Clover
{quote}

We want to make sure:
* remove clover license file and reference to it.
* build can still pass
* if we provide code coverage test during make, it needs to have some alternative after getting ride of the tool.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)