[
https://issues.jboss.org/browse/JBIDE-15392?page=com.atlassian.jira.plugi...
]
Snjezana Peco commented on JBIDE-15392:
---------------------------------------
We can change the required method to
public String[] getJarsAndFolders(String configuration)
The method would return modules' jars included into the configuration as well as
bundles, jboss-modules.jar for AS >=7.0 and
common, lib, server, server/{configuration}/lib, server/{configuration}/deploy/lib,
server/{configuration}/deployers, server/{configuration}/deploy/jbossweb.sar
for AS < 7.0.
If you can't add the method to JBossServerType, add it wherever you want. I will try
to adapt the PR.
However, I think the PR already works good enough. It is only the Search Lookup helping us
to find a server type/class using the Java Search lookup and doesn't have any effect
on a runtime.
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