[jbosstools-issues] [JBoss JIRA] (JBIDE-15392) Add api in server needed for source lookup
[
https://issues.jboss.org/browse/JBIDE-15392?page=com.atlassian.jira.plugi...
]
Rob Stryker commented on JBIDE-15392:
-------------------------------------
common, lib, server , server/default/lib, server/default/deploy/lib,
server/default/deployers, server/default/deploy/jbossweb.sar for AS <= 6.x.
I note that you say it should use server/default/lib, but, often times, the chosen
server or runtime is not in default mode. This seems a very bad assumption. Current code
in as.classpath makes sure to factor in the current configuration (server/all,
server/default, server/default2, etc)
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