#1000920
- Created on2012-02-29 12:58
- Reported by
- StatusFixed
- PriorityHighest (1)
- Assigned to
- Milestone
- Plan Level-
- Due Date-
Failed to Open Declaration via the popup menu
****Right click on any identifier and a popup menu will open, click on `Open Declaration`. Nothing will happen. While pressing F3 will correctly jump to the definition.
Example:
I think we absolutely need to fix this for 2.0.1 (during a training I was asked why the Scala IDE doesn't provide jump on definition like IDEA, that's bad :))
Example:
object Main {
println("Hello") // <- put the cursor in between `println`, then right click on it and select `Open Declaration`
}I think we absolutely need to fix this for 2.0.1 (during a training I was asked why the Scala IDE doesn't provide jump on definition like IDEA, that's bad :))
Leave a comment
on 2012-02-29 12:59 *
By Mirco Dotta
Description changed from Right click on any identifi... to Right click on any identifi...
Priority changed from Normal (3) to Highest (1)
(In revision:d43126db924b6f0d138588652db491e0de856b3a) Open Declaration via the context menu now works as expected.
When the user right clicks on a element and select "Open Declaration" in the
context menu, an instance of ``OpenAction`` is used to resolve the binding and
jump to the declaration.
Because the Eclipse API does not expose an extension point for this action, I
had to create a custom extension point (using AJDT), which allows weaving in to
JDT and can be used to intercept the creation of ``OpenAction``, if it
originates from a Scala editor.
This seem to be the only solution, which does not involve creating our own
Scala Editor. Hopefully, we will be able to remove this custom extension point
once we implement the Scala Editor (this is planned for Milestone 2 of the
Scala IDE Helium). Using AJDT for customizing the behavior of ``OpenAction``
was also suggested by Andrew Eisenberg in the following StackOverflow question:
http://stackoverflow.com/questions/1882053/how-can-i-define-a-custom-action-for-open-declaration-shortcut-f3-in-eclipse
Fix #1000920.
Branch: issue/open-declaration-fails-from-popup-menu-1000920
When the user right clicks on a element and select "Open Declaration" in the
context menu, an instance of ``OpenAction`` is used to resolve the binding and
jump to the declaration.
Because the Eclipse API does not expose an extension point for this action, I
had to create a custom extension point (using AJDT), which allows weaving in to
JDT and can be used to intercept the creation of ``OpenAction``, if it
originates from a Scala editor.
This seem to be the only solution, which does not involve creating our own
Scala Editor. Hopefully, we will be able to remove this custom extension point
once we implement the Scala Editor (this is planned for Milestone 2 of the
Scala IDE Helium). Using AJDT for customizing the behavior of ``OpenAction``
was also suggested by Andrew Eisenberg in the following StackOverflow question:
http://stackoverflow.com/questions/1882053/how-can-i-define-a-custom-action-for-open-declaration-shortcut-f3-in-eclipse
Fix #1000920.
Branch: issue/open-declaration-fails-from-popup-menu-1000920
on 2012-03-06 15:39 *
By Mirco Dotta
(In revision:e2c0ba50566c7be58d6c0ce8e550119cedd037ae) Open Declaration via the context menu now works as expected.
When the user right clicks on a element and select "Open Declaration" in the
context menu, an instance of ``OpenAction`` is used to resolve the binding and
jump to the declaration.
Because the Eclipse API does not expose an extension point for this action, I
had to create a custom extension point (using AJDT), which allows weaving in to
JDT and can be used to intercept the creation of ``OpenAction``, if it
originates from a Scala editor.
This seem to be the only solution, which does not involve creating our own
Scala Editor. Hopefully, we will be able to remove this custom extension point
once we implement the Scala Editor (this is planned for Milestone 2 of the
Scala IDE Helium). Using AJDT for customizing the behavior of ``OpenAction``
was also suggested by Andrew Eisenberg in the following StackOverflow question:
http://stackoverflow.com/questions/1882053/how-can-i-define-a-custom-action-for-open-declaration-shortcut-f3-in-eclipse
Fix #1000920.
(cherry picked from commit d43126db924b6f0d138588652db491e0de856b3a)
Branch: release/scala-ide-2.0.x
When the user right clicks on a element and select "Open Declaration" in the
context menu, an instance of ``OpenAction`` is used to resolve the binding and
jump to the declaration.
Because the Eclipse API does not expose an extension point for this action, I
had to create a custom extension point (using AJDT), which allows weaving in to
JDT and can be used to intercept the creation of ``OpenAction``, if it
originates from a Scala editor.
This seem to be the only solution, which does not involve creating our own
Scala Editor. Hopefully, we will be able to remove this custom extension point
once we implement the Scala Editor (this is planned for Milestone 2 of the
Scala IDE Helium). Using AJDT for customizing the behavior of ``OpenAction``
was also suggested by Andrew Eisenberg in the following StackOverflow question:
http://stackoverflow.com/questions/1882053/how-can-i-define-a-custom-action-for-open-declaration-shortcut-f3-in-eclipse
Fix #1000920.
(cherry picked from commit d43126db924b6f0d138588652db491e0de856b3a)
Branch: release/scala-ide-2.0.x
on 2012-03-14 15:35 *
By Mirco Dotta
(In revision:d43126db924b6f0d138588652db491e0de856b3a) Open Declaration via the context menu now works as expected.
When the user right clicks on a element and select "Open Declaration" in the
context menu, an instance of ``OpenAction`` is used to resolve the binding and
jump to the declaration.
Because the Eclipse API does not expose an extension point for this action, I
had to create a custom extension point (using AJDT), which allows weaving in to
JDT and can be used to intercept the creation of ``OpenAction``, if it
originates from a Scala editor.
This seem to be the only solution, which does not involve creating our own
Scala Editor. Hopefully, we will be able to remove this custom extension point
once we implement the Scala Editor (this is planned for Milestone 2 of the
Scala IDE Helium). Using AJDT for customizing the behavior of ``OpenAction``
was also suggested by Andrew Eisenberg in the following StackOverflow question:
http://stackoverflow.com/questions/1882053/how-can-i-define-a-custom-action-for-open-declaration-shortcut-f3-in-eclipse
Fix #1000920.
Branch: feature/scala-debugger-1000864
When the user right clicks on a element and select "Open Declaration" in the
context menu, an instance of ``OpenAction`` is used to resolve the binding and
jump to the declaration.
Because the Eclipse API does not expose an extension point for this action, I
had to create a custom extension point (using AJDT), which allows weaving in to
JDT and can be used to intercept the creation of ``OpenAction``, if it
originates from a Scala editor.
This seem to be the only solution, which does not involve creating our own
Scala Editor. Hopefully, we will be able to remove this custom extension point
once we implement the Scala Editor (this is planned for Milestone 2 of the
Scala IDE Helium). Using AJDT for customizing the behavior of ``OpenAction``
was also suggested by Andrew Eisenberg in the following StackOverflow question:
http://stackoverflow.com/questions/1882053/how-can-i-define-a-custom-action-for-open-declaration-shortcut-f3-in-eclipse
Fix #1000920.
Branch: feature/scala-debugger-1000864
