I guess there's no issue with just *using* software with a CPL license (for example, lots of apache projects use JUnit, which is also under the CPL).
But here's the issue. Files in the Toolkit are meant to be copied, then modified for a specific project, which lets that project override Toolkit defaults. But modifying those files creates derivative works under the CPL and those files can't be checked into an Apache source code repository.
So the derby community obviously needs to sort this out both near-term and long-term.
Ross suggested working with forrest on a plugin -- and I think you're seeing action related to that with his Jira entry. (My! that was fast!)
-jean
scott hutinger wrote:
Interesting that forrest has just issued a DITA issue for Forrest. I added the content for those interested.
http://issues.cocoondev.org/browse/FOR-461
Here is an overview of the issue: --------------------------------------------------------------------- Key: FOR-461 Summary: Create a DITA plugin Type: New Feature
Status: Unassigned Priority: Minor
Project: Forrest Fix Fors: 0.8
Assignee: Reporter: Ross Gardler
Created: Sat, 5 Mar 2005 3:54 AM Updated: Sat, 5 Mar 2005 3:54 AM
Description:
A DITA Toolkit is used for converting document source into human-consumable format, such as html, pdf, or whatever. So far, the SourceForge toolkit is the most interesting because it does what is needed:
http://mail-archives.eu.apache.org/mod_mbox/db-derby-dev/200503.mbox/[EMAIL PROTECTED]
--------------------------------------------------------------------- JIRA INFORMATION: This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators: http://issues.cocoondev.org//secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
