All Geronimo JARs should include a NOTICE.txt file in addition to the 
LICENSE.txt file
--------------------------------------------------------------------------------------

                 Key: GERONIMO-2308
                 URL: http://issues.apache.org/jira/browse/GERONIMO-2308
             Project: Geronimo
          Issue Type: Bug
      Security Level: public (Regular issues)
          Components: buildsystem
    Affects Versions: 1.1, 1.0
            Reporter: John Sisson
         Assigned To: John Sisson
            Priority: Blocker
             Fix For: 1.1.1


Currently Geronimo jars (e.g. the JARs for each application/module) do not 
contain a NOTICE.txt file under the META-INF directory.

The NOTICE.txt files in modules needs to contain attributions that are relevant 
for that module (not Geronimo as a whole).  For example, if the module has a 
dependency on a library that has a license requiring attributions upon use of 
the library (e.g. it has wording "Redistribution and use of this software" in 
the library license) then the module using the library should contain the 
attribution in the NOTICE.txt file.

Whilst reviewing attributions, the LICENSE.txt files for the modules and 
applications should also be updated to include the relevant licenses.

The following is a checklist to help track what has been done, in case someone 
wants to help out :-)

(x) applications\console-core
(x) applications\console-ear
(x) applications\console-framework
(x) applications\console-standard
(x) applications\daytrader
(x) applications\demo
(x) applications\ldap-realm-demo
(x) applications\magicGball
(x) applications\project.properties
(x) applications\remote-deploy
(x) applications\remote-deploy-lib
(x) applications\uddi-db
(x) applications\uddi-server
(x) applications\welcome

(x) modules\activation
(x) modules\activemq-embedded-rar
(x) modules\axis
(x) modules\axis-builder
(x) modules\client
(x) modules\client-builder
(x) modules\common
(x) modules\connector
(x) modules\connector-builder
(x) modules\console-web
(x) modules\converter
(x) modules\core
(x) modules\deploy-config
(x) modules\deploy-jsr88
(x) modules\deploy-tool
(x) modules\deployment
(x) modules\derby
(x) modules\directory
(x) modules\hot-deploy
(x) modules\installer-processing
(x) modules\installer-support
(x) modules\j2ee
(x) modules\j2ee-builder
(x) modules\j2ee-schema
(x) modules\javamail-transport
(x) modules\jetty
(x) modules\jetty-builder
(x) modules\jmx-remoting
(x) modules\kernel
(x) modules\mail
(x) modules\management
(x) modules\naming
(x) modules\naming-builder
(x) modules\project.properties
(x) modules\scripts
(x) modules\security
(x) modules\security-builder
(x) modules\service-builder
(x) modules\system
(x) modules\test-ddbean
(x) modules\timer
(x) modules\tomcat
(x) modules\tomcat-builder
(x) modules\transaction
(x) modules\upgrade
(x) modules\util
(x) modules\web-builder
(x) modules\webservices

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

        

Reply via email to