Running "mvn rat:check" generates a RAT (release audit tool) report in
target/rat.txt. The check fails since all the .php files in src/
examples/php and src/examples/resources do not have ASF Source
Header. src/examples/README.LICENSE explains a rationale, however
unless there has already been some determination on this, I would
raise this as an issue on the IPMC vote and think there is likely that
the IPMC would push back on the issue.
The examples are used with the @example phpdoc directive, so any ASF
header in the example body would be incorporated literally into the
generated documentation (as far as I can tell). So pointing the
phpdoc at the .php snippets with ASF license headers would not
generate pretty output. You could however point phpdoc at a directory
(target/examples) that was generated from the source removing the ASF
license using xslt or other processor. I can take a shot at that.
Since the generated docs could depend on the version of phpdoc
installed, I think it would be good to disclose the environment that
is used to build the release packages. Ideally a clean fresh
installed OS on an VM with just the minimum installed packages.
