Okay, I added license files for all included libs, and to Java sources.
I'm unable to add them to json files, since Python's json parser
doesn't handle comments (and they're not part of the json spec).
Once we get license headers added to C and C++, I think we're good to
go. Does anyone volunteer to do the C++ code?
I'm leaving for a short vacation tomorrow morning, and would really like
to get another release candidate build out for a vote before then...
Doug
Doug Cutting wrote:
Patrick Hunt wrote:
* rat tool reports a number of issues with licensing (see attached) of
source code files
Wow, that was a big attachment!
C and C++ sources need license headers added generally.
Outside of that, I see the following files that could use licenses:
!????? ./ivy.xml
!????? ./src/java/overview.html
!????? ./src/java/org/apache/avro/io/doc-files/parsing.html
!????? ./src/schemata/org/apache/avro/ipc/HandshakeRequest.m4
!????? ./src/schemata/org/apache/avro/ipc/HandshakeResponse.m4
!????? ./src/schemata/org/apache/avro/ipc/MD5.js
!????? ./src/test/java/org/apache/avro/io/TestBlockingIO.java
!????? ./src/test/java/org/apache/avro/io/TestParsingTable.java
!????? ./src/test/java/org/apache/avro/io/TestResolvingIO.java
!????? ./src/test/java/org/apache/avro/io/TestResolvingTable.java
!????? ./src/test/java/org/apache/avro/io/TestValidatingIO.java
!????? ./src/test/schemata/FSData.avpr
!????? ./src/test/schemata/interop.avsc
!????? ./src/test/schemata/simple.avpr
Pat, are there others that are of concern?
Doug