[
https://issues.apache.org/jira/browse/DERBY-6482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick Hillegas updated DERBY-6482:
---------------------------------
Attachment: derby-6482-02-aa-copyClasses.diff
Attaching derby-6482-02-aa-copyClasses.diff. This patch makes the build
machinery copy the compiled VTI demo classes into the demo directory of the
distribution. This patch also makes the top level demo page point at the
README.html in the VTI demo directory rather than the old README file which no
longer exists.
With these changes, I am able to successfully follow the instructions for the
VTI demo as they appear in a bin distribution.
You can test this yourself by first building a bin distribution. Here's how you
can build your own bin distribution without having to invoke the full and
disruptive top level release target:
1) First build the insane jars.
2) Build the full javadoc (invoke the top level javadoc target).
3) Then build the docs. It's sufficient to just build the html versions.
4) In your ant.properties file, point the docs.root variable at the root of
your docs client. This is the line I put in my ant.properties file:
{noformat}
docs.root=${user.home}/derby/docs/trunk
{noformat}
5) Now change directory to tools/release and run the following command:
{noformat}
ant bin.zip
{noformat}
This will drop a bin distribution into release/distributions
Touches the following files:
M java/demo/demo.html
M tools/release/build.xml
> Revamp the vti demo to look and behave more like the other demos.
> -----------------------------------------------------------------
>
> Key: DERBY-6482
> URL: https://issues.apache.org/jira/browse/DERBY-6482
> Project: Derby
> Issue Type: Improvement
> Components: Demos/Scripts
> Affects Versions: 10.11.0.0
> Reporter: Rick Hillegas
> Priority: Minor
> Attachments: derby-6482-01-aa-moveResources.diff,
> derby-6482-02-aa-copyClasses.diff
>
>
> The VTI demo began as a set of classes which could not be compiled by the
> normal build because they used Java 5 features. We hooked these classes into
> the ordinary build later on (see DERBY-3684). But the VTI demo still sticks
> out like a sore thumb. We ought to be able to make the VTI demo behave like
> the other demos now.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
