[DERBY-3196] UI plugin won't assign correct path when installed outside the 'plugins' directory, (in another extension location directory).

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 10.3.1.4
• Component/s: Eclipse Plug-in
• Labels: derby_triage10_5_2
• Environment: Windows 2000, Eclipse 3.3.1.1, Derby Plugin 10.3.1.4
• Urgency: Normal
• Issue & fix info: Repro attached, Workaround attached
• Assignee: Unassigned
• Reporter: Julen Parra
• Created: 10/Nov/07 19:11
• Updated: 15/Feb/11 21:08

Description

When installing the plugins in a directory other than the "plugins" directory, and setting the Derby nature to a project, the UI plugin will ignore that fact, and modify the classpath or the project as if the jar files were in the "plugins" directory.

How to reproduce:
Download and install both Derby plugins in a extension location, different from the plugins directory. To set up an alternative extension location, follow the instructions in:

http://www-128.ibm.com/developerworks/opensource/library/os-ecl-manage/

Start Eclipse, select a project and select the "Apache Derby->Add Apache Derby Nature" context menu option.
The project builds now with errors, as the system cannot find the derby jar files in the "ECLIPSE_HOME/plugins" directory.
Opening the classpath of the project, the jar files are added with the ECLIPSE_HOME/plugins path, even if they aren't there.

Solution:
The "Add Apache Derby Nature" should take into account the actual position of the plugins when changing the plugin.

Workaround:
Manually modify the Classpath. Add a new classpath variable called DERBY_HOME with the real directory where the derby jar files are located. Extend that variable with the jar files.