Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 46453 invoked from network); 26 Jun 2006 19:26:37 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 26 Jun 2006 19:26:37 -0000 Received: (qmail 16970 invoked by uid 500); 26 Jun 2006 19:26:37 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 16778 invoked by uid 500); 26 Jun 2006 19:26:36 -0000 Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: Delivered-To: mailing list derby-dev@db.apache.org Received: (qmail 16769 invoked by uid 99); 26 Jun 2006 19:26:36 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 26 Jun 2006 12:26:36 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=UNPARSEABLE_RELAY X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: local policy) Received: from [192.18.42.249] (HELO nwkea-pix-1.sun.com) (192.18.42.249) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 26 Jun 2006 12:26:32 -0700 Received: from d1-sfbay-05.sun.com ([192.18.39.115]) by nwkea-pix-1.sun.com (8.13.6+Sun/8.12.9) with ESMTP id k5QJQCOo029318 for ; Mon, 26 Jun 2006 12:26:12 -0700 (PDT) Received: from conversion-daemon.d1-sfbay-05.sun.com by d1-sfbay-05.sun.com (Sun Java System Messaging Server 6.2-4.02 (built Sep 9 2005)) id <0J1H00G01F7J7D00@d1-sfbay-05.sun.com> (original mail from David.Vancouvering@Sun.COM) for derby-dev@db.apache.org; Mon, 26 Jun 2006 12:26:12 -0700 (PDT) Received: from [192.9.61.102] by d1-sfbay-05.sun.com (Sun Java System Messaging Server 6.2-4.02 (built Sep 9 2005)) with ESMTPSA id <0J1H00FENFBNF900@d1-sfbay-05.sun.com> for derby-dev@db.apache.org; Mon, 26 Jun 2006 12:26:12 -0700 (PDT) Date: Mon, 26 Jun 2006 12:26:14 -0700 From: David Van Couvering Subject: Re: [jira] Closed: (DERBY-460) Create error message documentation out of code In-reply-to: <20002717.1151348551313.JavaMail.jira@brutus> Sender: David.Vancouvering@Sun.COM To: derby-dev@db.apache.org Message-id: <44A034D6.5040107@sun.com> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=UTF-8 Content-transfer-encoding: 7BIT References: <20002717.1151348551313.JavaMail.jira@brutus> User-Agent: Thunderbird 1.5.0.2 (X11/20060427) X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N I submitted a script, but it does not appear to be being used. Unless I'm missing something? David Jeff Levitt (JIRA) wrote: > [ http://issues.apache.org/jira/browse/DERBY-460?page=all ] > > Jeff Levitt closed DERBY-460: > ----------------------------- > > Resolution: Duplicate > > David Van Couvering long ago submitted a script that takes care of this, so I am cancelling my own bug.... > >> Create error message documentation out of code >> ---------------------------------------------- >> >> Key: DERBY-460 >> URL: http://issues.apache.org/jira/browse/DERBY-460 >> Project: Derby >> Type: Improvement > >> Components: Build tools >> Environment: all >> Reporter: Jeff Levitt >> Priority: Minor >> Fix For: 10.2.0.0 > >> As David suggested in the following thread: >> http://mail-archives.apache.org/mod_mbox/db-derby-dev/200507.mbox/%3c42D59CB9.5050308@Sun.COM%3e >> We need a way to generate a DITA file for the Reference Manual from the messages themselves, so that when new messages are added or changes are made, they are propogated to the documentation. The requirements are: >> - Some way of keeping metadata for the DITA file (parameter values, user response, explanation) in comments within the messages file, or perhaps using an XML document to store the data and the strings? >> - A script or xsl transform that reads the messages and generates the DITA file, adding the metadata where necessary. >> - A script to do a one-time conversion of the DITA file to the messages file (whether it be the current method of storing message plus comments or an XML file) so that existing messages will be in the new format. Then, any new messages must follow the format. >