[
https://issues.jboss.org/browse/JBIDE-15392?page=com.atlassian.jira.plugi...
]
Rob Stryker commented on JBIDE-15392:
-------------------------------------
Don't you need to know the list of module path that are to be
loaded too for AS >= 7
Currently we load specific hand-chosen folders for as >= 7, and we do not use any
configuration information to discover these.
I've been adjusting my patch to allow for an additional entry point with a
Map<String, String> where things such as the configuration folder may be passed in.
We usually get this from the runtime object, but in the case of just a server home, this
isn't possible, and so we will depend on a map of string properties passed in to
override or default these values.
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