[jbosstools-issues] [JBoss JIRA] (JBIDE-14993) SOA-P is not recognized as SOA-P and also cannnot be because of broking structure

[Max Rydahl Andersen (JIRA)]

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

Max Rydahl Andersen commented on JBIDE-14993:
---------------------------------------------

FYI, the main need is the version since users need to be able to tell two SOA-P's from each other and we also need to adjust behaviors dependent on the version of the installation.

ie. EAP 5 and EAP 6 are very different beasts, EAP 6.1 smaller difference, but different and my guess is that 6.2, ... 7, ..etc. will introduce other differences we need to adjust for.

Thus just knowing an install is SOA or EAP is not enough in it self.
                
> SOA-P is not recognized as SOA-P and also cannnot be because of broking structure
> ---------------------------------------------------------------------------------
>
>                 Key: JBIDE-14993
>                 URL: https://issues.jboss.org/browse/JBIDE-14993
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: server
>            Reporter: Max Rydahl Andersen
>            Assignee: Rob Stryker
>            Priority: Blocker
>             Fix For: 4.1.0.Beta2, 4.1.0.CR1
>
>
> from JBIDE-13582 SOA-P seem to have broken dir layout:
> It contains
> slot=soa
> in the bin/product.conf file.
> The /modules/system/layers/base/org/jboss/as/product/soa/dir/META-INF is expected, but the distribution contains /modules/system/layers/base/org/jboss/as/product/eap/dir/META-INF.

--
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: http://www.atlassian.com/software/jira