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

[Snjezana Peco (JIRA)]

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

Snjezana Peco commented on JBIDE-15392:
---------------------------------------

{quote}
Wouldn't it be the simplest to be able to create a class that provides all these default settings for the server type based on result from the beanloaders ?
{quote}

The API Rob created within this PR (RuntimeJarUtility) works this way. The only thing he would need to add is using a default configuration for JBoss AS < 7.0.

{quote}
And seriously - why can't sourcelookup just know about the runtime and if it does not know about it simply just return all jars ? then all this custom knowledge in sourcelookup goes away ?
{quoute}

A source lookup container knows only a home directory because it can be used for non JBoss servers as well as for servers that aren't defined in Eclipse. This API should provide all jars from JBoss servers (excluding application's jars) based on a home directory.
                
> 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
>             Fix For: 4.2.0.Alpha1
>
>
> 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