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

[Rob Stryker (JIRA)]

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

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

Adding this to JBossServerType does not really make sense, as most of the code already handling similar functionality is in the as.classpath plugin. The current code depends on archives.webtools integration plugin, which makes use of the fileset behavior inside archives.core. 

Because of the dependence on archives, it can not belong in the same plugin JBossServerType does, since as.wtp.core is our lowest-level API plugin and has 0 dependencies on archives. 

So, because
  1) Most code is already in as.classpath, and 
  2) It requires integration with project archives' directory scanner mechanism, 

It clearly belongs inside as.classpath. 
                
> 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