[
https://jira.jboss.org/browse/ARQ-164?page=com.atlassian.jira.plugin.syst...
]
Aslak Knutsen updated ARQ-164:
------------------------------
Fix Version/s: 1.0.0.Beta1
It is a quick fix in it self, but it's really only a symptom of a hack and needs some
redesign.. which is not 100% clear how yet.
Core needs a DeployableContianer in classpath to get the Active configuration that can
tell it which Profile to use.
Core should start up and work fine with out it, the Active Container Profile should rather
append to the current Context like the Suite/Class/TestContextAppenders in SPI work.
NPE in DeployableTestBuilder
----------------------------
Key: ARQ-164
URL:
https://jira.jboss.org/browse/ARQ-164
Project: Arquillian
Issue Type: Bug
Components: Deployable Containers SPI
Affects Versions: 1.0.0.Alpha2
Reporter: Jesper Pedersen
Fix For: 1.0.0.Beta1
Attachments: arq164.diff, DeployableTestBuilderTestCase.java
I get:
java.lang.NullPointerException
at
org.jboss.arquillian.impl.DeployableTestBuilder.build(DeployableTestBuilder.java:82)
at
org.jboss.arquillian.impl.DeployableTestBuilder.build(DeployableTestBuilder.java:71)
at org.jboss.arquillian.junit.Arquillian.<init>(Arquillian.java:68)
at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
Any component that uses a SPI implementation should guard against null values - if there
is a non-null requirement of course - and throw an IllegalArgumentException with a
descriptive error message.
--
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