Deployment order in org.jboss.cdi.tck.tests.deployment.packaging.ejb.EJBJarDeploymentTest is causing failure in GlassFish

Recent changes in GlassFish to account for resource validation during deployment as caused org.jboss.cdi.tck.tests.deployment.packaging.ejb.EJBJarDeploymentTest to fail. According to Bill Shannon:
"Still, all resource references must be mapped to actual resources at deployment time. If there's an EJB reference that can't be mapped to a real EJB at deployment time, because the EJB hasn't been deployed yet, deployment must fail."

"In reading back over it, I admit it's not as clear as it should be. It's a combination of what's said in EE.8.1.3 and the fact that the resource references are described as requirements of the application."

Martin has agreed to exclude this test for now and address it in the next TCK release. A simple fix is to change the deployment order from

@Deployment(name = "EJB", order = 2, testable = false)
public static JavaArchive createEjbtArchive() {

@Deployment(name = "TEST", order = 1)
public static WebArchive createTestArchive() {

to

@Deployment(name = "EJB", order = 1, testable = false)
public static JavaArchive createEjbtArchive() {

@Deployment(name = "TEST", order = 2)
public static WebArchive createTestArchive() {

I will create a PR for this.