[
https://issues.jboss.org/browse/JBIDE-15392?page=com.atlassian.jira.plugi...
]
Rob Stryker commented on JBIDE-15392:
-------------------------------------
Version bump would definitely be required for maintenance. Maintenance should continue
using hard-coded for now.
It would be just good the API to return jars for a default
configuration for JBoss AS < 7.0. That isn't obliged, but can be easily added.
I will add this to the PR. I have separated the PR into 2 commits. One is an api cleanup
(moving some classes, marking stuff as internal, etc) and the second is the addition of
the new test, new API class, etc. I will look into adding an additional method ot the API
class to pass in 'default' or its equivilent for all server types (ie,
standalone.xml for as7, and "default" for as<7).
The PR has been updated to just show the additions.
Good work all around.
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