[arquillian-issues] [JBoss JIRA] Updated: (ARQ-365) Clear up use of ProfileName, not the same as ProfileKey in ProfileService

[Aslak Knutsen (JIRA)]

     [ https://issues.jboss.org/browse/ARQ-365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Aslak Knutsen updated ARQ-365:
------------------------------

           Status: Resolved  (was: Pull Request Sent)
    Fix Version/s: jbossas_1.0.0.CR1
       Resolution: Done


pushed upstream

> Clear up use of ProfileName, not the same as ProfileKey in ProfileService
> -------------------------------------------------------------------------
>
>                 Key: ARQ-365
>                 URL: https://issues.jboss.org/browse/ARQ-365
>             Project: Arquillian
>          Issue Type: Bug
>          Components: Documentation, JBoss Containers
>    Affects Versions: 1.0.0.Alpha4
>            Reporter: Aslak Knutsen
>            Assignee: Karel Piwko
>             Fix For: jbossas_1.0.0.CR1
>
>
> profileName is used in Managed and Embedded to specify which server profile (directory) to use; "default", "standard", "all", etc
> Later the same value is used to load the ProfileService profile.
> profileName is used with Remote to specify which ProfileService profile to load.
> This is wrong. The ProfileService Profile is either "deployments", "deployers" or "farm", referring to the directory within the server profile(+ how to install them in MC). 
> From Arquillians point of view, the ProfileService Profile should always be "deployments", and the profileName configuration option can be removed from the Remote containers.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira