11:55 a.m.
Aslak Knutsen created ARQ-895:
---------------------------------
Summary: 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: 1.0.0.CR7
Reporter: Karel Piwko
Assignee: Aslak Knutsen
Priority: Critical
Fix For: 1.1.0.Beta1
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:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:57 a.m.
[
https://issues.jboss.org/browse/ARQ-895?page=com.atlassian.jira.plugin.sy...
]
Aslak Knutsen updated ARQ-895:
------------------------------
Fix Version/s: spock_1.0.0.next
(was: 1.1.0.Beta1)
Description:
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.
was:
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.
Affects Version/s: spock_1.0.0.Alpha1
(was: 1.0.0.CR7)
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.next
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:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:02 p.m.
[
https://issues.jboss.org/browse/ARQ-895?page=com.atlassian.jira.plugin.sy...
]
Aslak Knutsen updated ARQ-895:
------------------------------
Status: Pull Request Sent (was: Open)
Git Pull Request: https://github.com/arquillian/arquillian-testrunner-spock/pull/4
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.next
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:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:47 p.m.
[
https://issues.jboss.org/browse/ARQ-895?page=com.atlassian.jira.plugin.sy...
]
Aslak Knutsen updated ARQ-895:
------------------------------
Status: Closed (was: Pull Request Sent)
Resolution: Done
pushed upstream
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.next
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:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:20 p.m.
[
https://issues.jboss.org/browse/ARQ-895?page=com.atlassian.jira.plugin.sy...
]
Aslak Knutsen updated ARQ-895:
------------------------------
Fix Version/s: spock_1.0.0.Alpha2
(was: spock_1.0.0.next)
Git Pull Request: https://github.com/arquillian/arquillian-testrunner-spock/pull/4
(was: https://github.com/arquillian/arquillian-testrunner-spock/pull/4)
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:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:20 p.m.
[
https://issues.jboss.org/browse/ARQ-895?page=com.atlassian.jira.plugin.sy...
]
Aslak Knutsen reopened ARQ-895:
-------------------------------
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.next
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:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:15 p.m.
[
https://issues.jboss.org/browse/ARQ-895?page=com.atlassian.jira.plugin.sy...
]
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:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
4357
days inactive
4443
days old
arquillian-issues@lists.jboss.org
6 comments
1 participants
participants (1)
-
Aslak Knutsen (JIRA)