[ http://issues.apache.org/jira/browse/GERONIMO-2537?page=all ]
Kevan Miller updated GERONIMO-2537:
-----------------------------------
Attachment: geronimo-NoLicense.txt
I generated this list using ARAT (http://code.google.com/p/arat/)
svn export https://svn.apache.org/repos/asf/geronimo/server/trunk
geronimo-trunk
cd geronimo-trunk/
java -jar ../arat/rat/rat-0.2-SNAPSHOT.jar . > geronimo-arat.out
grep ==[a-z,A-Z] geronimo-arat.out
Some guidelines for src headers are here --
http://www.apache.org/legal/src-headers.html. A small excerpt is below:
With few exceptions, all human-readable Apache-developed files that are
included within a distribution must include the header text. Documentation,
including web site documentation distributed with the release, may include the
header text within some form of metadata (such as HTML comments) or as a header
or footer appearing in the visible documentation.
A file without any degree of creativity in either its literal elements or its
structure is not protected by copyright law; therefore, such a file does not
require a license header. If in doubt about the extent of the file's
creativity, add the license header to the file.
> All Geronimo source files must be brought in line with the new ASF source
> header and copyright notice policy
> ------------------------------------------------------------------------------------------------------------
>
> Key: GERONIMO-2537
> URL: http://issues.apache.org/jira/browse/GERONIMO-2537
> Project: Geronimo
> Issue Type: Task
> Security Level: public(Regular issues)
> Affects Versions: 1.1.2, 1.2
> Reporter: Kevan Miller
> Assigned To: Jacek Laskowski
> Priority: Blocker
> Fix For: 1.1.2, 1.2
>
> Attachments: geronimo-copyright.txt, geronimo-NoLicense.txt
>
>
> The ASF has new requirements for Source headers and copyright notices. See
> http://www.apache.org/legal/src-headers.html for details.
> All releases after November 1, 2006 must comply with this policy. It seems
> that 1.2 will be post November 1... :-)
> All Geronimo source files in trunk must be brought in line with this new
> policy... If we create a 1.1.2 release, we need to insure that all src files
> in branches/1.1 are brought inline with this new policy, also.
> There seem to be some scripts that will aid with these updates (see the FAQ
> in the above url). However, I can't access them at the moment...
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
