[jbosstools-issues] [JBoss JIRA] (JBIDE-14993) SOA-P is not recognized as SOA-P because tooling does not follow spec properly.

[Rob Stryker (JIRA)]

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

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

I'd also like to mention that unzipping soa-p currently has very strange behavior. Because there are multiple of the same files, users must always overwrite existing files. If they do not, they will end up with an installation where slot=eap instead of slot=soa in product.conf.  Debugging this kills the hour. 

If you unzip it, you must overwrite all. If you unzip in a script, make sure to unzip -o {soa-6.0.0.etcetc} to ensure overwrites. 
                
> SOA-P is not recognized as SOA-P because tooling does not follow spec properly. 
> --------------------------------------------------------------------------------
>
>                 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