Bug 542741 - Allow multiple attached source locations for a JAR/class folder on the Java build path
Summary: Allow multiple attached source locations for a JAR/class folder on the Java b...
Status: NEW
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 4.8   Edit
Hardware: PC Mac OS X
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-Core-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2018-12-13 05:27 EST by Bug Menot CLA
Modified: 2023-02-16 13:32 EST (History)
0 users

See Also:

Attachments
idea support multiple src locations (100.47 KB, image/png)
2018-12-13 05:27 EST, Bug Menot CLA 		no flags Details
View All 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 Bug Menot CLA 2018-12-13 05:27:51 EST 
Created attachment 276921 [details]
idea support multiple src locations

https://bugs.eclipse.org/bugs/show_bug.cgi?id=96670
```copy from #96670
Some projects, like Apache XmlBeans, package class files from multiple source
directories into a single jar file.  Since it is not possible to attach multiple
source locations to a jar, it is not possible to view the source for all classes
for the jar in the editor.

An alternative would be for eclipse to scan subdirectories of the attached
source location when looking fo source.  This would allow specification of the
parent for multiple source directories.
```
like idea, for reference only.
Comment 1 Eclipse Genie CLA 2020-12-03 11:31:02 EST 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.
Comment 2 Eclipse Genie CLA 2023-02-16 13:32:21 EST 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.