db-jdo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Bouschen (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (JDO-441) Update license information in all source files
Date Mon, 01 Jan 2007 19:29:27 GMT

     [ http://issues.apache.org/jira/browse/JDO-441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Michael Bouschen resolved JDO-441.
----------------------------------

    Resolution: Fixed

I updated the license header. You find more details here: http://wiki.apache.org/jdo/FixingLicenseHeader
I checked in the changes, one checkin per JDO subproject:
- api11: 491551
- api20: 491552
- btree: 491553
- enhancer20: 491555
- fostore20: 491556
- model20: 491557
- query20: 491558
- ri11: 491559
- runtime20: 491560
- tck11: 491564
- tck20: 491566
- util20: 491567
- top-level directory: 491568

> Update license information in all source files
> ----------------------------------------------
>
>                 Key: JDO-441
>                 URL: http://issues.apache.org/jira/browse/JDO-441
>             Project: JDO
>          Issue Type: Improvement
>          Components: api11, api2, btree, core2, enhancer2, fostore2, model2, query2,
ri11, runtime2, tck11, tck2, util2
>    Affects Versions: JDO 2 final
>            Reporter: Craig Russell
>         Assigned To: Michael Bouschen
>             Fix For: JDO 2 maintenance release 1
>
>
> There is a new Apache policy regarding license notices in source files. Please see http://www.apache.org/legal/src-headers.html
for details.
> What we need to do is to remove the Apache copyright notice header for source files and
replace it with the license header described in the reference.
> This applies to .java, .orm, .jdo files in the source tree. Everywhere there is currently
an Apache copyright notice needs to be updated.
> We also need to double check the distribution artifacts to make sure that the LICENSE
and NOTICE files conform to the new policy.

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

        

Mime
View raw message