[ http://issues.apache.org/jira/browse/DERBY-1986?page=comments#action_12447470 ] Jean T. Anderson commented on DERBY-1986: -----------------------------------------
Generalized the bis_DERBY.rdf DOAP file, revision 471596, to eliminate maintenance for new Derby releases. The longer story follows. [EMAIL PROTECTED] manages the files under www.apache.org/licenses/exports/ and I asked them for help initially building the site and also to understand the two different DOAP styles I noticed: James has more encompassing entries that span releases and MyFaces lists each release separately. The initial version I checked in for Derby adopted the MyFaces strategy, with the disadvantage that it requires the DOAP file to be updated with each new release and also requires www.apache.org/licenses/exports/ to be rebuilt. Here's a summary of the discussion on [EMAIL PROTECTED]: since the id of source distributions at archive.apache.org/dist/db/derby/ is pretty obvious, 'src' being in the file name for source distributions, we can point to that higher level directory like James does. Also Derby does not implement nor include the JCE (if Derby did implement/include and if the bits comprising the JCE were to change, new DOAP entries would be needed). So, this latest change to bis_DERBY.rdf eliminates the requirement to update the ASF exports info when new Derby distributions are released. > Add crypto notice for users and provide info for ASF exports page > ----------------------------------------------------------------- > > Key: DERBY-1986 > URL: http://issues.apache.org/jira/browse/DERBY-1986 > Project: Derby > Issue Type: Task > Components: Miscellaneous > Affects Versions: 10.2.1.6 > Reporter: Jean T. Anderson > Assigned To: Jean T. Anderson > Priority: Blocker > Fix For: 10.2.1.8, 10.3.0.0, 10.1.3.1, 10.0.2.1 > > Attachments: bis_DERBY.rdf, derby_crypto.txt > > > Derby doesn't implement nor include any cryptographic software, but it can > take advantage of the JCE. So, Derby needs to: > (1) Include a crypto notice in its README and downloads; see > http://www.apache.org/dev/crypto.html > (2) Provide an RDF file with information for the ASF export page at > http://www.apache.org/licenses/exports/ ; see > http://mail-archives.apache.org/mod_mbox/www-legal-discuss/200609.mbox/[EMAIL > PROTECTED] > Here's seed information for the user notice (please comment and add more): > Apache Derby interfaces with the Java Cryptography Extension (JCE) API to > provide: > - Full on-disk encryption of database files > - Storage and authentication of user passwords stored in the database > - User and password encryption over a network > Apache Derby does not include any implementation of JCE. -- 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
