javaee7-samples
javaee7-samples copied to clipboard
BasicAuthenticationStatelessTest fails due to failed deployment
Running mvn clean package -Pwildfly-managed-arquillian fails the BasicAuthenticationStatelessTest
Running org.javaee7.jaspic.basicauthentication.BasicAuthenticationStatelessTest
11:20:28,626 INFO [org.jboss.as.server.deployment] (MSC service thread 1-15) JBAS015876: Starting deployment of "c6a9a937-6bdf-4302-959f-30ba35aa57ad.war" (runtime-name: "c6a9a937-6bdf-4302-959f-30ba35aa57ad.war")
11:20:28,693 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 2) JBAS014613: Operation ("deploy") failed - address: ([("deployment" => "c6a9a937-6bdf-4302-959f-30ba35aa57ad.war")]) - failure description: {"JBAS014771: Services with missing/unavailable dependencies" => ["jboss.undertow.deployment.default-server.default-host./c6a9a937-6bdf-4302-959f-30ba35aa57ad.UndertowDeploymentInfoService is missing [jboss.security.security-domain.jaspitest]"]}
11:20:28,694 ERROR [org.jboss.as.server] (management-handler-thread - 2) JBAS015870: Deploy of deployment "c6a9a937-6bdf-4302-959f-30ba35aa57ad.war" was rolled back with the following failure message: {"JBAS014771: Services with missing/unavailable dependencies" => ["jboss.undertow.deployment.default-server.default-host./c6a9a937-6bdf-4302-959f-30ba35aa57ad.UndertowDeploymentInfoService is missing [jboss.security.security-domain.jaspitest]"]}
I am facing the same problem. I believe repo should be in the state where build should always work. Otherwise there is little to no benefit for providing broken samples.
By looking at Wildfly CI profile it's been broken for quite a while (interestingly enough GF profile has even more tests failures).
I think we should introduce CI-build per pull-request, something like this would be very helpful http://blog.kabisa.nl/2013/11/05/building-github-pull-requests-with-jenkins/
@arun-gupta is it on the roadmap?
@bartoszmajsak this was my intention with #206. Unfortunately I didn't have any time for this since JavaLand, sorry.
@aheusingfeld Ok, the issue description was a bit misleading then :)