Dan, I have disabled the test case for now as it fails on the bamboo server.
The test wants to configure a keystore and a truststore that are not in cxf's test resources. Unfortunately, this test works in the IDE since other transports do have the required files in their test resources and those folders are on the classpath in the IDE but not when running from Maven.
Adding keystore and truststore to cxf's test resources blows up the test in a different location ... leaving this for you to fix.
Dirk Olmes added a comment - 29/Sep/08 09:52 AM Dan, I have disabled the test case for now as it fails on the bamboo server.
The test wants to configure a keystore and a truststore that are not in cxf's test resources. Unfortunately, this test works in the IDE since other transports do have the required files in their test resources and those folders are on the classpath in the IDE but not when running from Maven.
Adding keystore and truststore to cxf's test resources blows up the test in a different location ... leaving this for you to fix.
The CXF build depends on the HTTP test-jar, so that is where it gets those resources. Seems you're right in that I only tested it from eclipse though as that resource loading refused to work from Maven... I'll dig into it. Thanks!
Dan Diephouse added a comment - 29/Sep/08 08:21 PM The CXF build depends on the HTTP test-jar, so that is where it gets those resources. Seems you're right in that I only tested it from eclipse though as that resource loading refused to work from Maven... I'll dig into it. Thanks!
Bug
Open
Major
HttpSecurityTestCase fails
The test wants to configure a keystore and a truststore that are not in cxf's test resources. Unfortunately, this test works in the IDE since other transports do have the required files in their test resources and those folders are on the classpath in the IDE but not when running from Maven.
Adding keystore and truststore to cxf's test resources blows up the test in a different location ... leaving this for you to fix.