Bug 11422 - Attaching source when using variables to point to jars very unintuitive
Summary: Attaching source when using variables to point to jars very unintuitive
Status: RESOLVED DUPLICATE of bug 12013
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 2.0   Edit
Hardware: PC Windows NT
: P3 normal (vote)
Target Milestone: 2.0 M5   Edit
Assignee: Philipe Mulet CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-03-14 17:51 EST by Leon Pesenson CLA
Modified: 2002-03-25 11:05 EST (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Leon Pesenson CLA 2002-03-14 17:51:32 EST
To make my project more portable, I decided to use the variables feature. The 
variables work fine, but attaching the source is very unintuitive. I used 
Xerces 1.4.4 and cos.jar from O'Reily as my test cases. Both come with src code 
in zip files. In addition to defining a variable for each jar file, I defined a 
variable for the source archives. For cos.jar the Src.zip had all the package 
directories starting at the root, so there was no problem. For Xerces the 
packages are not at the root. So I had to define a variable, so the only one 
that made sense was to use an empty SRC variable (which I could then reuse) and 
add the extension from that using the Extension button. I do not understand why 
the Extension could not be used without the empty variable. If I create a 
variable specific to each library then it works.
Comment 1 Philipe Mulet CLA 2002-03-25 11:05:04 EST
There was a bug in the variable resolution code leading it to treat a variable 
bound to "" as an unbound variable, and the extension path was then ignored.

The fix will be released into next integration build.

*** This bug has been marked as a duplicate of 12013 ***