[
https://issues.jboss.org/browse/JBIDE-10803?page=com.atlassian.jira.plugi...
]
Max Rydahl Andersen commented on JBIDE-10803:
---------------------------------------------
if we add the management api's as direct dependencies that screws up classloading
afaik and makes it impossible to install multiple versions as7 management API afaics.
And yes, I was not talking about plugin dependencies but example dependencies.
I'm not completely following what you mean by this:
"definning the JBoss AS 7.x/EAP 6 servers/runtimes in as.management.* plugins
(as.core could be installed without as.management.* plugins, but wouldn't include
JBoss AS 7.x/EAP 6 servers/runtimes)"
Why should as.management.* have server/runtimes ? the intent of as.management.* is to
allow for multiple versions of the management API over time to be used by server/runtimes.
JBoss AS 7.0.2 server start not detected
----------------------------------------
Key: JBIDE-10803
URL:
https://issues.jboss.org/browse/JBIDE-10803
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: central, JBossAS/Servers, updatesite
Affects Versions: 3.3.0.Beta1
Environment: Eclipse Java Indigo x86_64, installed only central,central community
& dependencies
JBoss Tools nightly build 3.3.0.v20120205-1417-H4165-Beta1
Fedora 16, 64b
JBoss AS 7.0.2
Reporter: Radim Hopp
Assignee: Nick Boldt
Fix For: 3.3.0.Beta3
When trying to start JBoss AS server, the server is started correctly, but IDE won't
recognize that it's already started (job "Starting <server name>"
won't end).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira