[
https://issues.jboss.org/browse/JBIDE-19799?page=com.atlassian.jira.plugi...
]
Rob Stryker commented on JBIDE-19799:
-------------------------------------
I'm not really sure we can do this. The classpaths are on a per-runtimeType basis.
Allowing users to 'browse' for their given module would require a specific
installation to browse, and if they choose to browse one specific runtime, it's
possible that the module they find is not in other runtimes of the same server type.
I could allow them to browse an existing runtime, simply for ease-of-use, but there's
no guarantee the module will be in all such installations, or that it's showing all
possible in other runtimes with the same runtimeType but extensions added on.
Ok yeah, I guess I can do something here to help.
JBoss Modules classpath option should guide users more
------------------------------------------------------
Key: JBIDE-19799
URL:
https://issues.jboss.org/browse/JBIDE-19799
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: server
Affects Versions: 4.3.0.Alpha2
Reporter: Rob Stryker
See
https://issues.jboss.org/browse/JBIDE-19789 for more info.
Max said: "but sounds like we could actually provide guidance to user which modules
and slots are available. But thats separate issue."
And now it *is* a separate issue ;)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)