Bug 445635 - Source attachment: allow attaching non-java source code to a library
Summary: Source attachment: allow attaching non-java source code to a library
Status: NEW
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 4.5   Edit
Hardware: All All
: P3 enhancement with 1 vote (vote)
Target Milestone: ---   Edit
Assignee: JDT-Core-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: helpwanted
Depends on:
Blocks:
 
Reported: 2014-10-01 08:03 EDT by Serban Iordache CLA
Modified: 2014-11-10 09:14 EST (History)
3 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Serban Iordache CLA 2014-10-01 08:03:04 EDT
Due to the rise in popularity of alternative languages for the JVM, an increasing number of libraries contain classes generated from non-java source code. In many cases, a library is the result of combining several JVM languages.

As implied by its name, the "Java Source Attachment" option is currently restricted to java source code. 

I propose extending the source attachment mechanism in order to support multiple source code types.
Comment 1 Jay Arthanareeswaran CLA 2014-11-10 04:01:58 EST
Hi Serban,

Is your proposal about supporting 'multiple' source attachment for the same library or is there something about supporting different types of source attachments? For former we do have bug 173641.
Comment 2 Serban Iordache CLA 2014-11-10 05:21:30 EST
The proposal is about supporting different types of source attachments (but allowing multiple source attachments would complement nicely this proposal).

Let us suppose my project references a jar that contains classes compiled from java, groovy and clojure. In this case, the source attachment folder (or jar, or zip) will contain .java, .groovy and .clj files.
Eclipse should be able to associate the correct source file to each compiled class.
Comment 3 Jay Arthanareeswaran CLA 2014-11-10 09:14:22 EST
Interesting proposal. But I am afraid the JDT core team will be able to promise anything on this. However, if anyone can work on this and provide a good quality patch, we will be happy to include this. Let me remind you that there might be involvement from the UI side too, so copying Markus on the bug.