In xdocs generated by Maven - typically the standard project reports - there is a copyright statement in favour of the Apache Software Foundation. IANAL, but this can't be right: the supplier of an authoring system doesn't get to assert copyright over documents made with that system. The copyright is only in the xdoc XML and doesn't get propagated to the HTML on the deployed web-site.
Description
In xdocs generated by Maven - typically the standard project reports - there is a copyright statement in favour of the Apache Software Foundation. IANAL, but this can't be right: the supplier of an authoring system doesn't get to assert copyright over documents made with that system. The copyright is only in the xdoc XML and doesn't get propagated to the HTML on the deployed web-site.
IANAL either (and thank god for that), but this seems ok to me. The copyright statement only appears in intermediate files that are used by maven to generate the final result. They are basically just templates (which are Apache copyrighted) with some values filled in. They are not supposed to be used or deployed.
The only possible problem I could see is in some rss files generated by some plugins (changes, checkstyle ...?), which contain a hardcoded Apache copyright statement . I'm not sure if this is ok, but in any case, that's an issue of the corresponding plugin and should be filed there.
Lukas Theussl added a comment - 01/Sep/05 01:42 PM IANAL either (and thank god for that), but this seems ok to me. The copyright statement only appears in intermediate files that are used by maven to generate the final result. They are basically just templates (which are Apache copyrighted) with some values filled in. They are not supposed to be used or deployed.
The only possible problem I could see is in some rss files generated by some plugins (changes, checkstyle ...?), which contain a hardcoded Apache copyright statement . I'm not sure if this is ok, but in any case, that's an issue of the corresponding plugin and should be filed there.
Bug
Open
Minor
Apache copyright statement in xdocs generated by Maven
IANAL either (and thank god for that), but this seems ok to me. The copyright statement only appears in intermediate files that are used by maven to generate the final result. They are basically just templates (which are Apache copyrighted) with some values filled in. They are not supposed to be used or deployed.
The only possible problem I could see is in some rss files generated by some plugins (changes, checkstyle ...?), which contain a hardcoded Apache copyright statement . I'm not sure if this is ok, but in any case, that's an issue of the corresponding plugin and should be filed there.