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

[Rob Stryker (JIRA)]

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

Rob Stryker commented on JBIDE-14993:
-------------------------------------

confusion is only due to us not knowing where to find the full product version info ;)  It seems obvious to me now that we may have several versions depending on the layers, and this will make things a bit less clean. I'm not sure i can solve THAT issue for now, but, as long as i can solve the majority of the cases you listed, things should be fine. I have a mental model that works for me now ;) 

Moving along as fast as i can. 
                
> 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