[
https://issues.apache.org/jira/browse/DERBY-6482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13904378#comment-13904378
]
Kim Haase commented on DERBY-6482:
----------------------------------
I created a second patch for DERBY-6459 to incorporate the changes you made for
DERBY-6256. I'm wondering if it might make sense to commit the existing patch
(with the other demo changes) and then file another one for future VTI changes.
> 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
>
> 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)
