[
https://issues.jboss.org/browse/ARQ-959?page=com.atlassian.jira.plugin.sy...
]
Jakub Narloch commented on ARQ-959:
-----------------------------------
On implementation level this may be quite appealing, because the profiles need to be
activated before the configuration is loaded. So the application context will have to be
first instantiated and after the profiles activation the configuration will loaded with
load(), classes or scan() method. This will affect the current support for custom context
classes, which could not be any more instantiated by passing the configuration through the
constructor.
Allow enabling Spring profiles through the tests
------------------------------------------------
Key: ARQ-959
URL:
https://issues.jboss.org/browse/ARQ-959
Project: Arquillian
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Reporter: Jakub Narloch
Assignee: Jakub Narloch
Labels: spring
Fix For: spring_1.0.0.next
Spring 3.1 introduces profiles for running in different environment. With each profile
can ben associated different Spring configuration. It should be possible for each test to
enable set of profiles using annotation e.g. @SpringActiveProfiles.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira