Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 37318 invoked from network); 30 Nov 2009 06:42:26 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 30 Nov 2009 06:42:26 -0000 Received: (qmail 63591 invoked by uid 500); 30 Nov 2009 06:42:26 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 63518 invoked by uid 500); 30 Nov 2009 06:42:26 -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 Delivered-To: moderator for derby-dev@db.apache.org Received: (qmail 61250 invoked by uid 99); 30 Nov 2009 02:17:18 -0000 X-ASF-Spam-Status: No, hits=-0.6 required=10.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_MED,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) MIME-Version: 1.0 In-Reply-To: <1698986731.1258827519876.JavaMail.jira@brutus> References: <25898779.1195826143480.JavaMail.jira@brutus> <1698986731.1258827519876.JavaMail.jira@brutus> Date: Sun, 29 Nov 2009 21:16:45 -0500 Message-ID: Subject: Re: [jira] Updated: (DERBY-3225) Some demo programs in -bin distributions are not mentioned in demo/programs/readme.html From: George Bova To: derby-dev@db.apache.org Content-Type: multipart/alternative; boundary=000e0cd2297aac32a704798d3be0 X-Virus-Checked: Checked by ClamAV on apache.org --000e0cd2297aac32a704798d3be0 Content-Type: text/plain; charset=ISO-8859-1 unsubscribe grscott@archivex.net On Sat, Nov 21, 2009 at 1:18 PM, Bryan Pendleton (JIRA) wrote: > > [ > https://issues.apache.org/jira/browse/DERBY-3225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel] > > Bryan Pendleton updated DERBY-3225: > ----------------------------------- > > Attachment: derby-3225.diff > > As I understand it, there are two changes needed: > > 1) Ensure that localcal/build.xml and scores/build.xml make it into the > binary release distribution. > (VTIs does not seem to have a separate build script) > 2) Ensure that localcal, scores, and vtis are mentioned, at least briefly, > in the top-level > readme.html, to give some overview to the user about what is to be found > there. > > Attached is a simple patch proposal to perform these two changes. > > I didn't build an entire release (don't know how), but I did test the > changes > in a separate standalone Ant test, and they seemed to work fine. > > The README files in localcal, scores, and vtis are not HTML, but just > simple text, so > they don't display very well in browsers, but at least they are better than > nothing, > and the motivated user can do more work themselves. > > Please let me know what you think. > > > Some demo programs in -bin distributions are not mentioned in > demo/programs/readme.html > > > --------------------------------------------------------------------------------------- > > > > Key: DERBY-3225 > > URL: https://issues.apache.org/jira/browse/DERBY-3225 > > Project: Derby > > Issue Type: Improvement > > Components: Demos/Scripts > > Affects Versions: 10.3.1.4 > > Environment: Derby -bin distributions > > Reporter: John H. Embretsen > > Assignee: Bryan Pendleton > > Attachments: derby-3225.diff > > > > > > Currently in trunk, there are 8 demo (sub)directories in the > demo/programs directory scheduled to be included in -bin distributions, each > containing one or more demo or sample applications: > > localcal/ > > nserverdemo/ > > scores/ > > simple/ > > simplemobile/ > > toursdb/ > > vtis/ > > workingwithderby/ > > With a -bin distribution of Derby, a user should be able to get an > overview of the included demo program offering by opening > demo/programs/readme.html in a web browser (there is a link to this from the > top-level index.html file). In trunk, we are currently missing short > descriptions of and links to: > > - localcal (see DERBY-1936) [also in 10.3] > > - scores (see DERBY-1993) [also in 10.3] > > - vtis (see DERBY-3129) > > Each of these demos have a README file in their respective > subdirectories, that could easily be linked to.* > > The remaining 5 demos are accessible from and described by the > readme.html file (readme.html is a frameset; the actual references and > descriptions are in navbar.html and demo.html. These files are placed in the > java/demo directory in the source tree). > > *) > > Also, one should make sure that the README files and other instructions > are suitable for -bin distributions, not only -src distributions or SVN > working copies. Otherwise, these particular demos should not be included in > -bin distributions. For example both localcal/README, scores/README and > vtis/README currently refer to build scripts that are not scheduled for > inclusion in -bin distros. > > -- > This message is automatically generated by JIRA. > - > You can reply to this email to add a comment to the issue online. > > --000e0cd2297aac32a704798d3be0 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable unsubscribe grscott@archivex.net

On Sat, Nov 21, 2009 at 1:18 PM, Bryan = Pendleton (JIRA) <j= ira@apache.org> wrote:

=A0 =A0 [ https://issues.apache.org/jira/browse/DERBY-3225?page=3Dcom.atlassi= an.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bryan Pendleton updated DERBY-3225:
-----------------------------------

=A0 =A0Attachment: derby-3225.diff

As I understand it, there are two changes needed:

1) Ensure that localcal/build.xml and scores/build.xml make it into the bin= ary release distribution.
=A0 (VTIs does not seem to have a separate build script)
2) Ensure that localcal, scores, and vtis are mentioned, at least briefly, = in the top-level
=A0 readme.html, to give some overview to the user about what is to be fou= nd there.

Attached is a simple patch proposal to perform these two changes.

I didn't build an entire release (don't know how), but I did test t= he <zipfileset> changes
in a separate standalone Ant test, and they seemed to work fine.

The README files in localcal, scores, and vtis are not HTML, but just simpl= e text, so
they don't display very well in browsers, but at least they are better = than nothing,
and the motivated user can do more work themselves.

Please let me know what you think.

> Some demo programs in -bin distributions are not mentioned in demo/pro= grams/readme.html
> ----------------------------------------------------------------------= -----------------
>
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Key: DERBY-3225
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 URL: https://issues.apache.org/jir= a/browse/DERBY-3225
> =A0 =A0 =A0 =A0 =A0 =A0 Project: Derby
> =A0 =A0 =A0 =A0 =A0Issue Type: Improvement
> =A0 =A0 =A0 =A0 =A0Components: Demos/Scripts
> =A0 =A0Affects Versions: 10.3.1.4
> =A0 =A0 =A0 =A0 Environment: Derby -bin distributions
> =A0 =A0 =A0 =A0 =A0 =A0Reporter: John H. Embretsen
> =A0 =A0 =A0 =A0 =A0 =A0Assignee: Bryan Pendleton
> =A0 =A0 =A0 =A0 Attachments: derby-3225.diff
>
>
> Currently in trunk, there are 8 demo (sub)directories in the demo/prog= rams directory scheduled to be included in -bin distributions, each contain= ing one or more demo or sample applications:
> =A0 localcal/
> =A0 nserverdemo/
> =A0 scores/
> =A0 simple/
> =A0 simplemobile/
> =A0 toursdb/
> =A0 vtis/
> =A0 workingwithderby/
> With a -bin distribution of Derby, a user should be able to get an ove= rview of the included demo program offering by opening demo/programs/readme= .html in a web browser (there is a link to this from the top-level index.ht= ml file). In trunk, we are currently missing short descriptions of and link= s to:
> =A0- localcal (see DERBY-1936) [also in 10.3]
> =A0- scores (see DERBY-1993) [also in 10.3]
> =A0- vtis (see DERBY-3129)
> Each of these demos have a README file in their respective subdirector= ies, that could easily be linked to.*
> The remaining 5 demos are accessible from and described by the readme.= html file (readme.html is a frameset; the actual references and description= s are in navbar.html and demo.html. These files are placed in the java/demo= directory in the source tree).
> *)
> Also, one should make sure that the README files and other instruction= s are suitable for -bin distributions, not only -src distributions or SVN w= orking copies. Otherwise, these particular demos should not be included in = -bin distributions. For example both localcal/README, scores/README and vti= s/README currently refer to build scripts that are not scheduled for inclus= ion in -bin distros.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


--000e0cd2297aac32a704798d3be0--