[richfaces-issues] [JBoss JIRA] (RF-13232) Enable flexible changing of the deployed archive name for general deployments, e.g. CoreDeployment

[Brian Leathem (JIRA)]

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

Brian Leathem commented on RF-13232:
------------------------------------

[~jhuska] your proposal sounds reasonable.  Would you like to formulate this as a Pull Request?
                
> Enable flexible changing of the deployed archive name for general deployments, e.g. CoreDeployment
> --------------------------------------------------------------------------------------------------
>
>                 Key: RF-13232
>                 URL: https://issues.jboss.org/browse/RF-13232
>             Project: RichFaces
>          Issue Type: Enhancement
>      Security Level: Public(Everyone can see) 
>          Components: tests - functional 
>    Affects Versions: 5.0.0.Alpha1
>            Reporter: Juraj Húska
>            Priority: Minor
>
> This should be added to support *[multiple deployments|https://docs.jboss.org/author/display/ARQ/Multiple+Deployments]* feature of Arquillian.
> It matters to the {{CoreDeployment}} and to the similar.
> Currently, {{Deployment}} class decide what name the deployed archive would have. It uses the passed {{class}} object to determine this. In the particular test, one needs to pass some class, which would be part of the name. The good practice is to pass the name of the test class.
> Here comes the problem with multiple deployments, when each deployed archive has to have different name.
> Proposed solution:
> Add overloaded constructor method, which would take a name for the deployed archive.

--
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