[JBoss JIRA] (ARQ-1635) Wrong SPI implementation registered for Standalone module
by Aslak Knutsen (JIRA)
[ https://issues.jboss.org/browse/ARQ-1635?page=com.atlassian.jira.plugin.s... ]
Aslak Knutsen closed ARQ-1635.
------------------------------
> Wrong SPI implementation registered for Standalone module
> ---------------------------------------------------------
>
> Key: ARQ-1635
> URL: https://issues.jboss.org/browse/ARQ-1635
> Project: Arquillian
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Spock TestRunner
> Affects Versions: spock_1.0.0.Beta2
> Reporter: Bartosz Majsak
> Assignee: Bartosz Majsak
> Fix For: spock_1.0.0.Beta3
>
>
> unable to run any tests, all resulted in a ClassNotFoundException:
> Caused by: java.lang.ClassNotFoundException: org.jboss.arquillian.junit.standalone.SpockStandaloneExtension
> Happens every time the runner tries to initialize services. The SpockStandaloneExtension class is on the classpath, but looks like it is in a different package: org.jboss.arquillian.spock.standalone.SpockStandaloneExtension
--
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, 3 months
[JBoss JIRA] (ARQ-1635) Wrong SPI implementation registered for Standalone module
by Aslak Knutsen (JIRA)
[ https://issues.jboss.org/browse/ARQ-1635?page=com.atlassian.jira.plugin.s... ]
Aslak Knutsen updated ARQ-1635:
-------------------------------
Fix Version/s: spock_1.0.0.Beta3
(was: spock_1.0.0.next)
> Wrong SPI implementation registered for Standalone module
> ---------------------------------------------------------
>
> Key: ARQ-1635
> URL: https://issues.jboss.org/browse/ARQ-1635
> Project: Arquillian
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Spock TestRunner
> Affects Versions: spock_1.0.0.Beta2
> Reporter: Bartosz Majsak
> Assignee: Bartosz Majsak
> Fix For: spock_1.0.0.Beta3
>
>
> unable to run any tests, all resulted in a ClassNotFoundException:
> Caused by: java.lang.ClassNotFoundException: org.jboss.arquillian.junit.standalone.SpockStandaloneExtension
> Happens every time the runner tries to initialize services. The SpockStandaloneExtension class is on the classpath, but looks like it is in a different package: org.jboss.arquillian.spock.standalone.SpockStandaloneExtension
--
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, 3 months
[JBoss JIRA] (ARQ-1618) Transaction extension configuration is not loaded early enough when working with ArquillianSuiteExtension
by Pëtr Andreev (JIRA)
[ https://issues.jboss.org/browse/ARQ-1618?page=com.atlassian.jira.plugin.s... ]
Pëtr Andreev commented on ARQ-1618:
-----------------------------------
Hi guys any update on the issue?
> 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
> Priority: Minor
>
> 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, 3 months