You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Jukka Zitting (JIRA)" <ji...@apache.org> on 2006/10/04 08:31:19 UTC

[jira] Updated: (JCR-573) Add missing license headers

     [ http://issues.apache.org/jira/browse/JCR-573?page=all ]

Jukka Zitting updated JCR-573:
------------------------------

    Attachment: JCR-573.patch

Attached a patch that to my best knowledge adds all missing license headers. I already got a confirmation from David for adjusting the files committed by Day employees, but there are also a few files (JMX files in JCR-RMI, JBoss files in JCA) from Edgar that need the license headers. Edgar, can you confirm that it's OK for me to add those license headers?

A few points worth notice:

* I implemented explicit comment support (the # syntax) for the database schema files to allow license headers
* I didn't add license headers to JAAS configuration files, since there seems to be no documented syntax for comments
* I didn't add license headers to the expected test output files to avoid comparison issues
* I assumed that the MIME type and HTTP status code lists in jcr-server are either original works or copies from within the ASF


> Add missing license headers
> ---------------------------
>
>                 Key: JCR-573
>                 URL: http://issues.apache.org/jira/browse/JCR-573
>             Project: Jackrabbit
>          Issue Type: Task
>            Reporter: Jukka Zitting
>         Assigned To: Jukka Zitting
>            Priority: Blocker
>             Fix For: 1.1
>
>         Attachments: JCR-573.patch
>
>
> There are a few source files and a number of other files with missing or incorrect license headers within the Jackrabbit source tree. See the  discusssion at http://thread.gmane.org/gmane.comp.apache.jackrabbit.devel/8698 for details. The missing license headers need to be added. 
> There are also W3C licensed files. This needs to be mentioned in the NOTICE file.

-- 
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