[JBoss JIRA] (ARQ-1647) Allow Executor to set process exit code
by Karel Piwko (JIRA)
Karel Piwko created ARQ-1647:
--------------------------------
Summary: Allow Executor to set process exit code
Key: ARQ-1647
URL: https://issues.jboss.org/browse/ARQ-1647
Project: Arquillian
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Extension - Spacelift
Affects Versions: spacelift_1.0.0.Alpha1
Reporter: Karel Piwko
Currently, it is not possible to setup exit code for external process. This makes handling of execution failure quite complicated.
Figure out what API should be used to let user define allowed exit values. 0 is to be kept as default value. Additionally, there might be multiple values to be set.
--
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
10 years, 10 months
[JBoss JIRA] (ARQ-1618) Transaction extension configuration is not loaded early enough when working with ArquillianSuiteExtension
by Aslak Knutsen (JIRA)
[ https://issues.jboss.org/browse/ARQ-1618?page=com.atlassian.jira.plugin.s... ]
Aslak Knutsen closed ARQ-1618.
------------------------------
> Transaction extension configuration is not loaded early enough when working with ArquillianSuiteExtension
> ---------------------------------------------------------------------------------------------------------
>
> Key: ARQ-1618
> URL: https://issues.jboss.org/browse/ARQ-1618
> Project: Arquillian
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: Extension - Transaction
> Affects Versions: transaction_1.0.0.Final
> Environment: Win7,CentOS
> Jboss7, Wildfly8
> Reporter: Pëtr Andreev
> Assignee: Bartosz Majsak
> Priority: Minor
> Fix For: transaction_1.0.1.Final
>
>
> The TransactionConfigurationProducer loads an extension configuration on demand using the BeforeSuite event. This behaviour appears to be insufficient when Aslak`s Brute Force Arquillian Suite Extension is in play, since the Suite Extension interferes the test case bootstrap process and enforces early usage of ARQ components.
> As a suggestion for TX-ext to support such a constellation the configuration loading of transaction extension can be moved right into the phase where ConfigurationRegistrar loads configurations and notifies observers about available ArquillianDescriptors.
--
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
10 years, 10 months
[JBoss JIRA] (ARQ-1618) Transaction extension configuration is not loaded early enough when working with ArquillianSuiteExtension
by Aslak Knutsen (JIRA)
[ https://issues.jboss.org/browse/ARQ-1618?page=com.atlassian.jira.plugin.s... ]
Aslak Knutsen updated ARQ-1618:
-------------------------------
Fix Version/s: transaction_1.0.1.Final
> Transaction extension configuration is not loaded early enough when working with ArquillianSuiteExtension
> ---------------------------------------------------------------------------------------------------------
>
> Key: ARQ-1618
> URL: https://issues.jboss.org/browse/ARQ-1618
> Project: Arquillian
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: Extension - Transaction
> Affects Versions: transaction_1.0.0.Final
> Environment: Win7,CentOS
> Jboss7, Wildfly8
> Reporter: Pëtr Andreev
> Assignee: Bartosz Majsak
> Priority: Minor
> Fix For: transaction_1.0.1.Final
>
>
> The TransactionConfigurationProducer loads an extension configuration on demand using the BeforeSuite event. This behaviour appears to be insufficient when Aslak`s Brute Force Arquillian Suite Extension is in play, since the Suite Extension interferes the test case bootstrap process and enforces early usage of ARQ components.
> As a suggestion for TX-ext to support such a constellation the configuration loading of transaction extension can be moved right into the phase where ConfigurationRegistrar loads configurations and notifies observers about available ArquillianDescriptors.
--
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
10 years, 10 months
[JBoss JIRA] (ARQ-1646) Add WildFly managed container
by Bartosz Majsak (JIRA)
Bartosz Majsak created ARQ-1646:
-----------------------------------
Summary: Add WildFly managed container
Key: ARQ-1646
URL: https://issues.jboss.org/browse/ARQ-1646
Project: Arquillian
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Extension - Persistence
Affects Versions: persistence_1.0.0.Alpha6
Reporter: Bartosz Majsak
Assignee: Bartosz Majsak
Priority: Trivial
Fix For: persistence_1.0.0.next
--
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
10 years, 10 months
[JBoss JIRA] (ARQ-1645) persistence doesn't support multiple datasources
by Bartosz Majsak (JIRA)
[ https://issues.jboss.org/browse/ARQ-1645?page=com.atlassian.jira.plugin.s... ]
Bartosz Majsak updated ARQ-1645:
--------------------------------
Fix Version/s: persistence_1.0.0.next
> persistence doesn't support multiple datasources
> ------------------------------------------------
>
> Key: ARQ-1645
> URL: https://issues.jboss.org/browse/ARQ-1645
> Project: Arquillian
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Extension - Persistence
> Affects Versions: persistence_1.0.0.Alpha6
> Reporter: Romain Manni-Bucau
> Assignee: Bartosz Majsak
> Fix For: persistence_1.0.0.next
>
>
> It is common to use multiple datsources (in fact all apps I'm working with does it) and ATM dbunit extension doesn't support multiple datsource init/asserts (UsingDataSet and ExpectedDataSet).
> Would be great to get a plural version of @DataSource and @XDataSet
--
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
10 years, 10 months
[JBoss JIRA] (ARQ-1645) persistence doesn't support multiple datasources
by Romain Manni-Bucau (JIRA)
Romain Manni-Bucau created ARQ-1645:
---------------------------------------
Summary: persistence doesn't support multiple datasources
Key: ARQ-1645
URL: https://issues.jboss.org/browse/ARQ-1645
Project: Arquillian
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Extension - Persistence
Affects Versions: persistence_1.0.0.Alpha6
Reporter: Romain Manni-Bucau
Assignee: Bartosz Majsak
It is common to use multiple datsources (in fact all apps I'm working with does it) and ATM dbunit extension doesn't support multiple datsource init/asserts (UsingDataSet and ExpectedDataSet).
Would be great to get a plural version of @DataSource and @XDataSet
--
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
10 years, 10 months