eclipse-archived
Allow Java projects to click on Ceylon declarations
Figure out if we can make Java projects that depend on Ceylon projects navigate to Ceylon types by clicking on them. ATM you get to the bytecode, which is not useful.
Eyeballing the code, it's not at all clear why this doesn't already work...
yes, that's what I thought also. Probably something in JavaSearch. I'll have a look.
In fact, it works for me. @FroMage you have to select Open Ceylon Declaration from the little drop down menu thingy, not just click.
To be clear: it only works if the Ceylon project exports its classpath containers.
OK, so I found that popup. For it to become visible I need to Ctrl-hover-move the mouse over the declaration for a second before it shows up. Just Ctrl-clicking it leads to the bytecode. That's not enough, guys, nobody can discover that.
Note that the tooltips could be improved too:
Open Declarationcom.foo.bar.CeylonType
@Ceylon
@SharedAnnotation$annotation$
Note: This element neither has attached source nor attached Javadoc and hence no Javadoc could be found.
For it to become visible I need to
Ctrl-hover-movethe mouse over the declaration for a second before it shows up. Just Ctrl-clicking it leads to the bytecode. That's not enough, guys, nobody can discover that.
Open an issue against Eclipse. On Mac the menu pops up immediately with no delay.
Note that the tooltips could be improved too:
What tooltips are these? I've never seen a tooltip like that.
@maxandersen Do you know how to make our hyperlink detector the first one in the Java editor?
I do not think there are a way to sort/order hyperlink detectors.
But I also do not think this is the right way to solve this issue.
If you are ending up with bytecode in an editor it is because the source lookup mechanism is not right. As I recall it you can add custom source code lookup to projects which will be activated when eclipse can't locate it - @fbricon might know of the best place to add these.
@maxandersen even if the source lookup was able to locate the Ceylon source code, that still wouldn't be good enough, since it would still not be enough to convince the Java editor to open the linked source code in the Ceylon editor instead of the Java editor.
do you know of a bug already open against JDT to fix that ? If not, lets get one open with this imo very valid usecase.