[
https://issues.apache.org/jira/browse/DERBY-6916?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bryan Pendleton updated DERBY-6916:
-----------------------------------
Attachment: docs.diff
rgsderbyrunjarsyntax.html
tadminappschangingyourclasspath.html
Thanks for the review and suggestions, Kim! Attached is
a revised copy of the Admin Guide page, as well as a
proposed enhancement to the Getting Started page.
> 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: 10.14.0.0
> Reporter: Bryan Pendleton
> Priority: Minor
> Attachments: adminguide.diff, docs.diff, rgsderbyrunjarsyntax.html,
> tadminappschangingyourclasspath.html, 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
(v6.3.4#6332)
