1:55 p.m.
[
https://jira.jboss.org/jira/browse/WELD-337?page=com.atlassian.jira.plugi...
]
David Allen commented on WELD-337:
----------------------------------
Other than using the trunk of weld core, the JBoss AS server is also updated with the
latest software from this build. In other words, in the core/jboss-as project, the
command "mvn install -Pupdate-jboss-as" is run to update that server with the
trunk version of Weld and the deployer.
I did checkin another change late yesterday where the build.properties file in
core/jboss-as still had a reference to the 5.2.0 deployer. That could be a problem, but
it didn't seem to have any effect in my platform. Can you double check if it is still
failing, and if so, whether or not the JBoss AS server is being updated with the correct
trunk version of Weld and the 6.0.0-SNAPSHOT (or at least 6.0.0.M1) version of the
deployer?
I can't follow the link that you included, so I am still not sure what exactly you are
seeing.
Unable to run cdi-tck (dist) tests against JBoss AS 6.0.x
---------------------------------------------------------
Key: WELD-337
URL: https://jira.jboss.org/jira/browse/WELD-337
Project: Weld
Issue Type: Bug
Affects Versions: 1.0.0.GA
Reporter: Martin Gencur
Assignee: David Allen
Priority: Critical
Fix For: 1.0.1.CR1
cdi-tck tests are executed in this job:
http://hudson.qa.jboss.com/hudson/view/Weld/job/Weld-tck-dist-incontainer...
Last successfull build is taken from JBossAS 6.0.x job and jsr299-tck-1.0.0-dist.zip is
used.
After starting the test run, the following exception is thrown (Cannot find any
implementations of TestLauncher, check that org.jboss.testharness.api.TestLauncher is
specified) :
16:42:04,214 INFO [htmlunit.WebClient] statusCode=[500] contentType=[text/html]
16:42:04,214 INFO [htmlunit.WebClient] <html><head><title>JBoss
Web/3.0.0.alpha-22 - Error report</title><style><!--H1
{font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:22px;}
H2
{font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:16px;}
H3
{font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:14px;}
BODY {font-family:Tahoma,Arial,sans-serif;color:black;background-color:white;} B
{font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;} P
{font-family:Tahoma,Arial,sans-serif;background:white;color:black;font-size:12px;}A {color
: black;}A.name {color : black;}HR {color : #525D76;}--></style>
</head><body><h1>HTTP Status 500 - </h1><HR size="1"
noshade="noshade"><p><b>type</b> Exception
report</p><p><b>message</b>
<u></u></p><p><b>description</b> <u>The server
encountered an internal error () that prevented it from fulfilling this
request.</u></p><p><b>exception</b>
<pre>javax.servlet.ServletException: Cannot find any implementations of
TestLauncher, check that org.jboss.testharness.api.TestLauncher is specified
javax.faces.webapp.FacesServlet.service(FacesServlet.java:323)
org.jboss.weld.servlet.ConversationPropagationFilter.doFilter(ConversationPropagationFilter.java:68)
</pre></p><p><b>root cause</b>
<pre>java.lang.IllegalArgumentException: Cannot find any implementations of
TestLauncher, check that org.jboss.testharness.api.TestLauncher is specified
org.jboss.testharness.properties.PropertiesManager.getClassValue(PropertiesManager.java:150)
org.jboss.testharness.properties.PropertiesManager.getInstanceValue(PropertiesManager.java:169)
org.jboss.testharness.impl.PropertiesBasedConfigurationBuilder.getInstanceValue(PropertiesBasedConfigurationBuilder.java:62)
org.jboss.testharness.impl.PropertiesBasedConfigurationBuilder.init(PropertiesBasedConfigurationBuilder.java:53)
org.jboss.jsr299.tck.impl.JSR299PropertiesBasedConfigurationBuilder.init(JSR299PropertiesBasedConfigurationBuilder.java:33)
org.jboss.jsr299.tck.impl.JSR299PropertiesBasedConfigurationBuilder.init(JSR299PropertiesBasedConfigurationBuilder.java:16)
org.jboss.testharness.impl.ConfigurationFactory.get(ConfigurationFactory.java:22)
org.jboss.jsr299.tck.tests.context.conversation.client.ConversationTestPhaseListener.beforePhase(ConversationTestPhaseListener.java:34)
com.sun.faces.lifecycle.Phase.handleBeforePhase(Phase.java:228)
com.sun.faces.lifecycle.Phase.doPhase(Phase.java:99)
com.sun.faces.lifecycle.RestoreViewPhase.doPhase(RestoreViewPhase.java:110)
com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:118)
javax.faces.webapp.FacesServlet.service(FacesServlet.java:310)
org.jboss.weld.servlet.ConversationPropagationFilter.doFilter(ConversationPropagationFilter.java:68)
</pre></p><p><b>note</b> <u>The full stack trace of
the root cause is available in the JBoss Web/3.0.0.alpha-22
logs.</u></p><HR size="1"
noshade="noshade"><h3>JBoss
Web/3.0.0.alpha-22</h3></body></html>
This exception causes almost all the tests fail. I tried to run this job locally with the
same result.
org.jboss.testharness.api.TestLauncher property is really specified in a file
jsr299/weld/jboss-tck-runner/src/main/resources/META-INF/jboss-test-harness.properties
(and jsr299/weld/jboss-tck-runner/target/classes/META-INF/jboss-test-harness.properties)
and the implementation of the TestLauncher is in directory
jsr299/lib/jboss-test-harness.jar
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira