My 2 cents are for not including derbyrun.jar. Since we don;t mention about how to use derbyrun.jar. May be we can include that and modify the plugin to use derbyrun.jar in the future...
Manjula On 3/19/08, Myrna van Lunteren <[EMAIL PROTECTED]> wrote: > > On 3/19/08, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > Myrna van Lunteren <[EMAIL PROTECTED]> writes: > > > > > I do wonder, whether the core plugin.xml has a problem as it doesn't > > > mention derbyrun.jar, although it is included...Maybe that was an > > > oversight from when derbyrun.jar was added to the plugin? If we fix > > > this, we will have to regenerate the core plugin. I think the release > > > candidate will be soon enough for that. > > > > Now that I've been through the process I don' mind spinning another beta > > :) Just let me know... > > > > > > -- > > dt > > > I really don't think it's necessary to make another beta. > > I tried to figure out where this change of including derbyrun.jar came > from, and it's because in the top level build.xml we're specifying > derby*.jar (excluding derbyLocale* and derbyTesting.jar). So when > derbyrun was invented, it got included automatically. However, the > core plugin.xml gets generated during the build by > org.apache.derbyBuild.eclipse.DerbyEclipsePlugin (source under > java/build), which doesn't add derbyrun to the list of jars. > > I'm not sure if we should exclude derbyrun.jar from the build process > so it doesn't get into the core plugin, or add it to the core plugin's > plugin.xml. The plugins were not designed to have it in, the plugin > documentation probably doesn't mention it. But maybe it should be > included and documented. > I'll do some further thinking about how one would use derbyrun.jar > from within eclipse, if anyone has an opinion? For now, I'm inclined > to think we should exclude derbyrun.jar in build.xml... > > Myrna > -- Thanks, Manjula.
