Configuration options should be loadable from multiple sources
--------------------------------------------------------------
Key: ARQ-284
URL: https://jira.jboss.org/browse/ARQ-284
Project: Arquillian
Issue Type: Feature Request
Components: Configuration
Reporter: Aslak Knutsen
Fix For: 1.0.0.Beta1
The configuration should be able to get configuration from multiple locations and override in some order..
system properties, properties file, maven config, arquillian.xml etc..
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Update Arquillian Drone build
-----------------------------
Key: ARQ-669
URL: https://issues.jboss.org/browse/ARQ-669
Project: Arquillian
Issue Type: Task
Security Level: Public (Everyone can see)
Reporter: Karel Piwko
Following modifications should be done:
* Should be able to build with Maven Central only
* Update JBoss parent
* Add SHRINKWRAP-273 fix for Java 5/6 compatibility
* Move Weld test Example to use Java EE 6 spec
--
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
@Expected annotation giving false positives due to improper usage of DBUnit assertions
--------------------------------------------------------------------------------------
Key: ARQ-663
URL: https://issues.jboss.org/browse/ARQ-663
Project: Arquillian
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Extension - Persistence
Reporter: Bartosz Majsak
--
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
Change Persistence TransactionStarted event to StartTransaction
---------------------------------------------------------------
Key: ARQ-654
URL: https://issues.jboss.org/browse/ARQ-654
Project: Arquillian
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Extension - Persistence
Affects Versions: persistence_1.0.0.Alpha1
Reporter: Aslak Knutsen
Fix For: persistence_1.0.0.next
Change the naming of the event to define what should happen, not what has happened. Since it's the Event that triggeres it, it hasn't actually happened yet.
StartTransaction vs TransactionStarted
TransactionStarted should in this case be switched with SPI level BeforeTransactionStarted and AfterTransactionStarted, see ARQ-652
--
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
Error when running a test that is not related with persistence
--------------------------------------------------------------
Key: ARQ-662
URL: https://issues.jboss.org/browse/ARQ-662
Project: Arquillian
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Extension - Persistence
Affects Versions: persistence_1.0.0.Alpha1
Reporter: Bartosz Majsak
Tries to load datasource even for tests which are not requiring persistence extensions. More details here: https://gist.github.com/1393355
--
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
Add Persistence configuration to Archive instead of client callback
-------------------------------------------------------------------
Key: ARQ-653
URL: https://issues.jboss.org/browse/ARQ-653
Project: Arquillian
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Extension - Persistence
Affects Versions: persistence_1.0.0.Alpha1
Reporter: Aslak Knutsen
Fix For: persistence_1.0.0.next
A Callback to the client side has a added overhead, adding the 'configuration' file to the deployment itself should speed it up
--
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
Prepare Weld Containers 1.0.0.CR3
---------------------------------
Key: ARQ-676
URL: https://issues.jboss.org/browse/ARQ-676
Project: Arquillian
Issue Type: Release
Security Level: Public (Everyone can see)
Components: Weld Containers
Reporter: Aslak Knutsen
Assignee: Aslak Knutsen
Fix For: weld_1.0.0.Final
--
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
@OperateOnDeployment to allow test to operate on 2 deployments
--------------------------------------------------------------
Key: ARQ-674
URL: https://issues.jboss.org/browse/ARQ-674
Project: Arquillian
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Affects Versions: 1.0.0.CR5
Reporter: Radoslav Husar
Priority: Critical
Fix For: 1.0.0.Final
Currently only 1 @OperateOnDeployment can be used on a @Test method. In clustering test, there are always at least 2 different deployments. @OperateOnDeployment should be able to specify 2 deployments in order to be able to use their metas.
I currently ended up with
{code}
// Ouch, hardcoded URL will need fixing. ARQ doesnt support @OperateOnDeployment on 2.
String url1 = baseURL.toString() + "simple";
String url2 = "http://127.0.0.1:8080/distributable/simple";
{code}
Link to docs
http://docs.jboss.org/arquillian/api/latest/org/jboss/arquillian/api/Oper...
--
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
OpenWebBeans container should support WebArchive deployments
------------------------------------------------------------
Key: ARQ-403
URL: https://issues.jboss.org/browse/ARQ-403
Project: Arquillian
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: OpenWebBeans Containers
Affects Versions: 1.0.0.Alpha5
Reporter: Aslak Knutsen
Priority: Minor
Fix For: 1.0.0.Beta1
OpenWebBeans integration only look for META-INF/beans.xml, should also look for WEB-INF/beans.xml.
And be able to load Bean definitions from WEB-INF/classes, and setup the Resource locations.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
Support OpenWebBeans 1.1 Container
----------------------------------
Key: ARQ-526
URL: https://issues.jboss.org/browse/ARQ-526
Project: Arquillian
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: OpenWebBeans Containers
Affects Versions: openwebbeans_1.0.0.CR1
Reporter: Aslak Knutsen
Fix For: openwebbeans_1.0.0.Final
API in OpenWebBeans has changed, addBeansXMLLocation has changed from URL to String.
Evaluate if we should use the OpenWebBeans SPIs instead of the extending AbstractMetaDataDiscovery
https://github.com/arquillian/arquillian-container-openwebbeans/blob/mast...
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira