[jbosstools-issues] [JBoss JIRA] (JBIDE-15392) Add api in server needed for source lookup

Rob Stryker (JIRA) jira-events at lists.jboss.org
Tue Sep 3 06:21:03 EDT 2013


    [ https://issues.jboss.org/browse/JBIDE-15392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12801079#comment-12801079 ] 

Rob Stryker commented on JBIDE-15392:
-------------------------------------

Here's a summary of the use cases as Fred and I understand them. Please correct any information that seems wrong so that I can proceed with the patch:

There are 3 use cases
    1: source lookup / identification : when you enter a java class from the server in debug, we need to access that jar, so we can do some source attachement. Works for *any* jar used by the server

    2: java search : in the IDE, user should be able to find any class from the server 'classpath'. IMO, that should be restricted to visible jars only

    3: actually adding jars to the classpath of a dynamic web project or other project

Items 2 and 3 should return identical jars, while item 1 should return a superset. 

                
> 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


More information about the jbosstools-issues mailing list