db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kim Haase (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-6916) Doc of derbyrun.jar should describe complete list of referenced jars
Date Mon, 07 Nov 2016 14:40:58 GMT

    [ https://issues.apache.org/jira/browse/DERBY-6916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15644354#comment-15644354

Kim Haase commented on DERBY-6916:

This is a really useful addition to the docs. Thanks, Bryan.

My only suggestions are to use code font to refer to the tools and jars in the new list items,
and possibly to reference this topic from the "Syntax for the derbyrun.jar file" topic in
the Getting Started manual.

> Doc of derbyrun.jar should describe complete list of referenced jars
> --------------------------------------------------------------------
>                 Key: DERBY-6916
>                 URL: https://issues.apache.org/jira/browse/DERBY-6916
>             Project: Derby
>          Issue Type: Improvement
>          Components: Documentation
>    Affects Versions:
>            Reporter: Bryan Pendleton
>            Priority: Minor
>         Attachments: adminguide.diff, tadminappschangingyourclasspath.html
> As I read our build.xml file:
> {quote}
> <manifest file="$
> Unknown macro: {derby.jar.dir}
> /lists/smfcmd.mf">
> <attribute name="Main-Class" value="org.apache.derby.iapi.tools.run"/>
> <attribute name="Class-Path" value="derby.jar derbyclient.jar derbytools.j
> ar derbynet.jar derbyoptionaltools.jar"/>
> </manifest>
> {quote}
> the derbyrun.jar filepulls both derbytools.jar and derbyoptionaltools.jar into my classpath.
> This means that both regular tools and optional tools can be run using only derbyrun.jar
in the classpath.
> I think this indicates that this documentation is incorrect:
> https://builds.apache.org/job/Derby-docs/lastSuccessfulBuild/artifact/trunk/out/adminguide/tadminappschangingyourclasspath.html
> because it seemed to me to quite explicitly say that derbyrun.jar includes *ONLY* derby.jar,
derbynet.jar, and derbyclient.jar.
> We should review that doc, and also any other doc that references derbyrun.jar, to make
sure it is clear what it references and how to use it.

This message was sent by Atlassian JIRA

View raw message