Return-Path: Delivered-To: apmail-forrest-dev-archive@www.apache.org Received: (qmail 24819 invoked from network); 3 Nov 2004 10:29:24 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 3 Nov 2004 10:29:24 -0000 Received: (qmail 542 invoked by uid 500); 3 Nov 2004 10:29:22 -0000 Delivered-To: apmail-forrest-dev-archive@forrest.apache.org Received: (qmail 498 invoked by uid 500); 3 Nov 2004 10:29:22 -0000 Mailing-List: contact dev-help@forrest.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: dev@forrest.apache.org Delivered-To: mailing list dev@forrest.apache.org Received: (qmail 486 invoked by uid 99); 3 Nov 2004 10:29:22 -0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (hermes.apache.org: domain of cjxaf-forrest-dev-1@m.gmane.org designates 80.91.229.2 as permitted sender) Received: from [80.91.229.2] (HELO main.gmane.org) (80.91.229.2) by apache.org (qpsmtpd/0.28) with ESMTP; Wed, 03 Nov 2004 02:29:22 -0800 Received: from list by main.gmane.org with local (Exim 3.35 #1 (Debian)) id 1CPIOF-0006KS-00 for ; Wed, 03 Nov 2004 11:29:19 +0100 Received: from host190-154.pool80204.interbusiness.it ([80.204.154.190]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 03 Nov 2004 11:29:19 +0100 Received: from nicolaken by host190-154.pool80204.interbusiness.it with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 03 Nov 2004 11:29:19 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: dev@forrest.apache.org From: Nicola Ken Barozzi Subject: Re: packaging our tools Date: Wed, 03 Nov 2004 11:29:15 +0100 Lines: 41 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: host190-154.pool80204.interbusiness.it User-Agent: Mozilla Thunderbird 0.8 (Windows/20040913) X-Accept-Language: en-us, en In-Reply-To: X-Enigmail-Version: 0.86.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime Sender: news X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N Dave Brondsema wrote: > I'm working on writing documentation for end-user installation of the XXE > configuration (in tools/xxe). > > The buildfile there builds a .zip which people can simply extract into > c:\program files\XMLmind_XML_Editor\config. > > If we build a release of forrest, what happens to this .zip file? I > imagine it would be something like this: > * As part of the main forrest build, the XXE build.xml is called * The .zip file that is created in build/xxe.zip > * Everything (src, and built files (build/xml-forrest.jar and the .zip in > question) is packed in to one apache-forrest-0.7-dev.zip I'm ok with this, and we can add that we should also release the jar and the zip separately. > And can we make this .zip file available seperate from forrest? There is > a current need for this since 0.6 does not include a built XXE > configuration. Future need may continue to exist, because people may want > to edit document-v13/20 files without installing forrest. This is the > case at the company I work for, because the writers commit their changes > to CVS and then we run forrestbot on our server. I took a look at the sources, and it seems that the only think that does not need Forrest to be usable is the xxe tool (oh, and forrestbar). For these, which are not subprojects but just extra tools, I agree that it does not make sense in having them necessarily packaged only with Forrest. The only thing to take care is to include the license and notice files in the zip, oh, and in the jar too. -- Nicola Ken Barozzi nicolaken@apache.org - verba volant, scripta manent - (discussions get forgotten, just code remains) ---------------------------------------------------------------------