Bug 67020 - Javadoc Locations: no support for variables
Summary: Javadoc Locations: no support for variables
Status: ASSIGNED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.0   Edit
Hardware: PC Windows 2000
: P5 enhancement with 17 votes (vote)
Target Milestone: ---   Edit
Assignee: JDT-UI-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
: 76629 (view as bug list)
Depends on:
Blocks:
 
Reported: 2004-06-14 12:33 EDT by Sasha Haghani CLA
Modified: 2015-08-03 21:41 EDT (History)
8 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Sasha Haghani CLA 2004-06-14 12:33:08 EDT 
It seems variables can't be used in definining the location of Javadoc
archives associated with a given project library.

This is a bit of nuisance since we store Javadoc in an archive alongside
our JARs and source archives and would like to define these globally for
all users of a project.
Comment 1 Philipe Mulet CLA 2004-06-18 07:18:21 EDT 
Javadoc support is handled outside JDTCore.
Comment 2 Martin Aeschlimann CLA 2005-05-12 10:44:20 EDT 
not for 3.1
Comment 3 Olivier Thomann CLA 2006-04-25 14:32:49 EDT 
*** Bug 76629 has been marked as a duplicate of this bug. ***
Comment 4 Denis Roy CLA 2009-08-30 02:20:00 EDT 
As of now 'LATER' and 'REMIND' resolutions are no longer supported.
Please reopen this bug if it is still valid for you.
Comment 5 Remy Suen CLA 2010-03-24 09:56:34 EDT 
This was brought up today on IRC. Denis swapped it from RESOLVED/LATER to RESOLVED/WONTFIX during the whole Bugzilla resolution/state debacle.

Is this indeed a WONTFIX?
Comment 6 Markus Keller CLA 2010-03-24 14:21:18 EDT 
(In reply to comment #5)
> Is this indeed a WONTFIX?

No, this could still be done, although we don't have plans to work on this. If someone comes up with a well thought out proposal and also wants to implement it, then we will review the contribution.

Points to consider:
- should not break existing APIs, e.g. org.eclipse.jdt.core.IClasspathAttribute.JAVADOC_LOCATION_ATTRIBUTE_NAME and all its clients
- should fit into the existing story (e.g. just add support for classpath variables for "var" entries on the build path)
- needs fixes in Core and UI
Comment 7 jon shusta CLA 2012-07-20 12:04:52 EDT 
+1 for supporting a new scheme separate from "jar:file:", e.g. "jar:path:"
Comment 8 Chris Miami CLA 2015-08-03 21:41:50 EDT 
Just as a matter of consistency, being able to specify a library using a variable but then having to add a concrete path to source and javadoc attachments is just counterproductive.  It defeats the purpose of using the variable at all because individual contributors must go in and reconfigure the paths each time they check out a project.