[
https://jira.jboss.org/jira/browse/JBIDE-3641?page=com.atlassian.jira.plu...
]
Rob Stryker updated JBIDE-3641:
-------------------------------
Attachment: JBIDE-3641.2.patch
Second try, fixes more.
The problems with this patch are that it does not give the runtime component for EAP
it's own namespace. I've tried desperately to fix it, however can't seem to do
it.
This isn't a huge problem as that can be changed later without ruining installations.
The server and runtimes each have "eap" added to the ID to differentiate
themselves, but the "runtime-component" section refuses to respond when I add an
eap.
Perhaps snjezana can help out with this.
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: Rob Stryker
Priority: Blocker
Fix For: 3.0.0.GA
Attachments: JBIDE-3641.2.patch
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