]
Martin Malina commented on JBIDE-16467:
---------------------------------------
bugzilla for removing generic jboss from server tools is here:
Streamline server groups in New Server dialog
---------------------------------------------
Key: JBIDE-16467
URL:
https://issues.jboss.org/browse/JBIDE-16467
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: server
Affects Versions: 4.2.0.Alpha1
Reporter: Martin Malina
Assignee: Rob Stryker
Fix For: 4.2.0.Beta1
Today I noticed that the group for JBoss EAP servers is now called Red Hat JBoss
Middleware (JBIDE-15269). Seeing it got me thinking that the way it is now is actually
pretty confusing and looks like a mess. Let me explain.
When you have JBoss Tools installed today, you get 3 JBoss-related groups in the New
Server dialog.
1. JBoss - this is in Eclipse by default. It contains very old servers only - up to JBoss
AS 5. Could we possibly lobby for getting this removed/replaced with our own adapters?
2. JBoss Community - this is where all our JBoss AS and Wildfly adapters are.
3. Red Hat JBoss Middleware - this contains all EAP servers.
When you try to look at it from a new user's perspective, somebody who doesn't
work at RH, it can give the impression that probably nobody took the time to put some
order to this - there are 3 different groups, not even next to one another (because
it's sorted alphabetically of course).
Granted, the Eclipse's JBoss group is not in our control, but maybe we can try to do
something there, too?
I'm not sure what's the solution here. But if we must use Red Hat JBoss
Middleware, couldn't we put everything in this group? Or are there any other
alternatives to the current state? Or is it just me who finds this confusing? Opinions
welcome.
--
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: