]
Aslak Knutsen closed ARQ-895.
-----------------------------
Resolution: Done
Arquillian config-impl-base is not a part of spock-standalone
-------------------------------------------------------------
Key: ARQ-895
URL:
https://issues.jboss.org/browse/ARQ-895
Project: Arquillian
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Base Implementation
Affects Versions: spock_1.0.0.Alpha1
Reporter: Karel Piwko
Assignee: Aslak Knutsen
Priority: Critical
Fix For: spock_1.0.0.Alpha2
Cloned from Core, but Spock has similar problem. Not adding config-impl-base means no
Extension configuration in standalone mode.
When configuration was split, the arquillian-config-impl-base was made a dependency of
container only
{code}
./container/spi/pom.xml:
<artifactId>arquillian-config-impl-base</artifactId> <!-- ILLEGAL
DEPENDENCY, fix with new Config module -->
./container/impl-base/pom.xml:
<artifactId>arquillian-config-impl-base</artifactId> <!-- ILEGAL
DEPENDENCY, resolved with new Config API -->
./bom/pom.xml:
<artifactId>arquillian-config-impl-base</artifactId>
./config/impl-base/pom.xml:
<artifactId>arquillian-config-impl-base</artifactId>
{code}
This means that when no container is on classpath, e.g. standalone mode of junit/testng,
ArquillianDescriptor is not created at all.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: