[JBoss JIRA] (JBIDE-14529) Support 'Open Declaration(F3)' on Resource lookup in Deployment methods
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14529?page=com.atlassian.jira.plugi... ]
Snjezana Peco commented on JBIDE-14529:
---------------------------------------
{quote}
One way is to use Ctrl+1 (quickfix) to add additional navigation. We do this for bringing JPA queries to the criteria editor in hibernate tools.
{quote}
We already have that feature via a hyperlink. See JBIDE-6338.
We can also add Ctrl+1 if you think that is a better solution.
Not sure if we can automatically open a resource using Ctrl+1 (quick fix). The first we get is the Quick fix dialog. Also, the dialog is opened wherever we click within the Java editor so we can't control it on the current selection.
> Support 'Open Declaration(F3)' on Resource lookup in Deployment methods
> -----------------------------------------------------------------------
>
> Key: JBIDE-14529
> URL: https://issues.jboss.org/browse/JBIDE-14529
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: testing-tools
> Reporter: Aslak Knutsen
> Assignee: Max Rydahl Andersen
> Fix For: 4.1.x, 4.2.x
>
>
> Given a deployment method with resource references
> When pressing 'open declaration(F3)'
> Then open the source file for the reference
> Not sure if this makes sense in Eclipse lingo, but I personally navigate code via F3 (Open Declaration) a lot. Navigating to JavaArchive.class via F3 but having to do 'Ctrl+Mouse Click' to get to the resource reference seems clumsy.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 7 months
[JBoss JIRA] (JBIDE-15392) Add api in server needed for source lookup
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15392?page=com.atlassian.jira.plugi... ]
Snjezana Peco commented on JBIDE-15392:
---------------------------------------
{quote}
Why don't the source lookup know which server it is ? How does it find the server dir if not through the related running server ? I know there is an option for just specifying a directory but wouldn't it make sense to be able to know which server thats being used or is that information lost ?
{quote}
We add only a home directory to the Search Lookup Source container because we can debug any server in the Source Lookup (tomcat, glassfish, ...) including a server that isn't defined in JBoss Tools/Eclipse (a remote server).
> Add api in server needed for source lookup
> ------------------------------------------
>
> Key: JBIDE-15392
> URL: https://issues.jboss.org/browse/JBIDE-15392
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: maven, server
> Reporter: Max Rydahl Andersen
> Assignee: Rob Stryker
>
> As uncovered in https://github.com/jbosstools/jbosstools-central/pull/128/files#L5L120 we got a problem with source lookup code always having to play catchup with server changes.
> We need to define a stable api that can be used here.
> lets outline what api is actually needed and then subjiras for the specifics.
> For me it looks like server lookup needs a few things:
> 0. know exact version of server
> 1. know the file structure of a certain server
> 2. get dir or directories that contain jar that is the "runtime"
> My guess is that #2 might just be sufficient for source code lookup.
> Any comments ?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 7 months