[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-8344) Runtime detection creates invalid runtime for EAP 4.3.0.GA_CP03

Magnus Mogren (JIRA) jira-events at lists.jboss.org
Tue Feb 8 02:40:39 EST 2011


    [ https://issues.jboss.org/browse/JBIDE-8344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12580674#comment-12580674 ] 

Magnus Mogren commented on JBIDE-8344:
--------------------------------------

No i have not, and relying on that does not sound like a good solution for the following reasons:

1) EAP_HOME is not required for the AS to run. I do fine without 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.

Maybe looking in the manifest.mf file of the jboss-system.jar file located in the lib directory of the AS is a better solution to find out what the AS version is?
For 4.3.0.GA_CP03 EAP it reads:
   Implementation-Title: JBoss [EAP]
   Specification-Version: 4.3.0.GA_CP03
For 4.2.3 AS:
   Implementation-Title: JBoss [Trinity]
   Specification-Version: 4.2.3.GA
And for 6.0.0 AS:
   Implementation-Title: JBoss Application Server System
   Specification-Version: 6.0.0.Final
   
I do not have another EAP than 4.3 available, but if the Implementation-Title in the manifest.mf of those also contains [EAP] then looking for that would work?


> 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

        


More information about the jbosstools-issues mailing list