Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 140816 - Relative path for the JAR in the jarList
Summary: Relative path for the JAR in the jarList
Status: CLOSED FIXED
Alias: None
Product: Data Tools
Classification: Tools
Component: Connectivity (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows 2000
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Brian Fitzpatrick CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-05-09 11:34 EDT by Nazmin CLA
Modified: 2008-07-29 14:41 EDT (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Nazmin CLA 2006-05-09 11:34:58 EDT
Provide a way to specify a relative path for the jarList of a driver. Currently, in my plugin, I specify a relative path for the jarList (such as 
runtime/jt400.jar) but when I check in the preference page or when I am 
creating a new connection profile it complains that the jar location is 
not found. This is because it's treating the relative path as an absolute 
path.
Comment 1 Rob Cernich CLA 2006-05-31 16:13:02 EDT
Hey Brian, could you document how to reference jar files located within plugins when defining a driver definition?  Thanks, Rob.
Comment 2 Brian Fitzpatrick CLA 2006-05-31 16:52:00 EDT
Hi. There is a way to do this currently. In the jarlist property for the driver, use the following syntax:

[plugin-id]/path

For example, if you have jar1.jar in the "my.jar.plugin" plugin in a directory called "folder/jars", it would look like:

[my.jar.plugin]/folder/jars/jar1.jar

Note that the jar file(s) must be exposed via plug-ins in order for this to work. 
Comment 3 Rob Cernich CLA 2006-07-20 14:39:34 EDT
driver management framework supports this.  marking as fixed.
Comment 4 Brian Fitzpatrick CLA 2008-07-01 17:35:31 EDT
Closing bugs
Comment 5 Cameron Bateman CLA 2008-07-29 14:15:27 EDT
Has this mechanism been proven to work for jar-bundled plugins or just directory bundled plugins.  In other words, if my plugin ships in the eclipse/plugins directory as a jar file rather than a sub-directory, will it be found?  So far we haven't had success with that use case.
Comment 6 Cameron Bateman CLA 2008-07-29 14:15:40 EDT
Has this mechanism been proven to work for jar-bundled plugins or just directory bundled plugins.  In other words, if my plugin ships in the eclipse/plugins directory as a jar file rather than a sub-directory, will it be found?  So far we haven't had success with that use case.
Comment 7 Brian Fitzpatrick CLA 2008-07-29 14:41:01 EDT
That's an interesting use case. I don't believe we tested for that case, as it hadn't come up yet. 

Can you open a new BZ entry for it and we'll look at it for 1.6.1?