[
https://issues.jboss.org/browse/JBIDE-15392?page=com.atlassian.jira.plugi...
]
Rob Stryker commented on JBIDE-15392:
-------------------------------------
The API in my as.classpath code which I am making 100% requires a IRuntime. This is
because for servers < 7, we MUST know what configuration they are using. We cannot
simply use 'default' as that doesn't make sense if the runtime is customized
to 'all' or 'myconfig'.
In AS7, as well, in the future there will be more customizations, and the ability to know
what jars are applicable to the server will evolve. It would make no sense to perform
these tasks without knowing what IRuntime they apply to.
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