[
https://issues.jboss.org/browse/JBIDE-8344?page=com.atlassian.jira.plugin...
]
Snjezana Peco commented on JBIDE-8344:
--------------------------------------
1) EAP_HOME is not required for the AS to run. I do fine without it.
The runtime detector doesn't recognize EAP when adding EAP_HOME/jboss_as as a
runtime path.
This is a bug and I will fix it.
2) It makes detecting several different EAP's impossible since
EAP_HOME can only point to one EAP. In the
screenshot EditRuntimeDialog2.png attached to
https://issues.jboss.org/browse/JBIDE-7527
several different
EAP's is detected.
You can unpack several different EAPs to the same directory and add the directory to the
JBoss Runtime Detection preferences page.
I have added some EAP, SOA, EPP, AS, Seams... to the e:\JBossRuntimes directory and the
e:\JBossRuntimes directory to the JBoss Runtime preferences page when creating the
EditRuntimeDialog2.png screenshot.
Runtime detection creates invalid runtime for EAP 4.3.0.GA_CP03
---------------------------------------------------------------
Key: JBIDE-8344
URL:
https://issues.jboss.org/browse/JBIDE-8344
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS
Affects Versions: 3.2.0.CR1
Reporter: Magnus Mogren
Assignee: Snjezana Peco
The automatic runtime detection cannot handle EAP 4.3.0.GA_CP03.
In the "Searching for runtimes..." dialog it detects it as Version=4.3 and
type=AS.
The created runtime gets type "JBoss AS 4.2" and vendor "JBoss
Community".
Because of this i get the warning "This server type expects a version of 4.2 but the
server directory is of version 4.3.0.GA_CP03." in the "Edit Server Runtime
Environment" dialog
The correct type and vendor should be "JBoss Enterprise Application Platform
4.3" and "JBoss Enterprise Middleware"
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira