[
https://jira.jboss.org/jira/browse/JBIDE-3641?page=com.atlassian.jira.plu...
]
Max Rydahl Andersen commented on JBIDE-3641:
--------------------------------------------
JBoss.org -> JBoss Community
JBoss, a division of Red Hat -> JBoss Enterprise Middleware
Icon will not have EAP in the name (i.e. it will be different from all others for the
moment), it will just be the JBoss, a division of Red Hat logo (attached)
JBoss EAP in the list of servers becomes JBoss Enterprise Application Platform
Similar, when we create the servers automatically the name should not include EAP but
Enterprise Application Platform.
Seperate .org servers from product servers
------------------------------------------
Key: JBIDE-3641
URL:
https://jira.jboss.org/jira/browse/JBIDE-3641
Project: Tools (JBoss Tools)
Issue Type: Task
Components: JBossAS
Affects Versions: 3.0.0.CR2
Reporter: Max Rydahl Andersen
Assignee: Max Rydahl Andersen
Priority: Blocker
Fix For: 3.0.0.GA
Attachments: JBIDE-3641.2.patch, JBIDE3641s.zip
Today we got "JBoss, a division of Red Hat" as the overarching category for our
servers and beneath it a set of JBoss AS xyz servers.
To make the seperation of .org and product bits clear I suggest we do the following:
JBoss, a division of Red Hat
JBoss EAP 4.3 (possibly JBoss Enterprise Application Platform 4.3)
JBoss.org
<the current list of servers>
Note: This server types is *not* intended to be extended with i.e. JBoss SOA-P and JBoss
EPP - these will all be based on EAP and are more something that is modelled well with
runtime components than a seperate server type.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira