I was running this as a vmware client running ubuntu 10.10. I am now going to try on ubuntu 12.04 native and see if perhaps there was an issue with udp and vmware or perhaps the old kernel (2.6.35)
On Mon, Oct 1, 2012 at 1:30 PM, Jason Pell <[email protected]> wrote: > well fancy that on 2.7.x I got past the jaxrs frontend and failed on > another test. I will rerun and see if it might just be a timing > issue. > > Tests in error: > testSimpleUDP(org.apache.cxf.transport.udp.UDPTransportTest): Timed > out waiting for response to operation > {http://apache.org/hello_world}greetMe. > > > > On Mon, Oct 1, 2012 at 1:19 PM, Jason Pell <[email protected]> wrote: >> All test pass I mean :) >> >> On Mon, Oct 1, 2012 at 1:19 PM, Jason Pell <[email protected]> wrote: >>> I have checked out trunk of cxf and will try to build again. I see >>> there are plans to release 2.7 soon anyway so little point working on >>> a patch for 2.6.x when I will be upgrading to 2.7. >>> >>> Hopefully I get a full build and all tests fail. >>> >>> Any ideas about what might have gone wrong with my attempts to build >>> 2.6 would be appreciated? Should I do a mvn -Pfastinstall install >>> first before a mvn install? >>> >>> What is the normal process you developers of cxf use? Be good if you >>> might be able to provide some details of your dev environment as well >>> - including Maven and Java versions. Any m2/settings.xml that you >>> needed to set? >>> >>> >>> >>> On Mon, Oct 1, 2012 at 12:41 PM, Jason Pell <[email protected]> wrote: >>>> Hi, >>>> >>>> I am trying to build cxf 2.6 branch with tests and it fails at >>>> cxf-rt-frontend-jaxrs. >>>> >>>> I am building with maven 3 and jdk 1.6.0_32 on linux (Ubuntu 10.10) >>>> >>>> I am just doing a mvn clean >>>> then a mv install >>>> >>>> The following tests fail: >>>> >>>> Failed tests: >>>> testCustomSchemaJaxbContextPrefixes(org.apache.cxf.jaxrs.model.wadl.WadlGeneratorTest): >>>> expected:<1> but was:<0> >>>> >>>> testExternalSchemaJaxbContextPrefixes(org.apache.cxf.jaxrs.model.wadl.WadlGeneratorTest): >>>> expected:<1> but was:<0> >>>> >>>> testExternalRelativeSchemaJaxbContextPrefixes(org.apache.cxf.jaxrs.model.wadl.WadlGeneratorTest): >>>> expected:<1> but was:<0> >>>> >>>> testExternalSchemaCustomPrefix(org.apache.cxf.jaxrs.model.wadl.WadlGeneratorTest): >>>> expected:<1> but was:<0> >>>> >>>> testCustomSchemaAndSchemaPrefixes(org.apache.cxf.jaxrs.model.wadl.WadlGeneratorTest): >>>> expected:<1> but was:<0> >>>> >>>> testSingleRootResource(org.apache.cxf.jaxrs.model.wadl.WadlGeneratorTest): >>>> expected:<1> but was:<0> >>>> >>>> testMultipleRootResources(org.apache.cxf.jaxrs.model.wadl.WadlGeneratorTest): >>>> expected:<1> but was:<0> >>>> >>>> >>>> I deleted my entire .m2/repository just in case I had some invalid >>>> jars lying around. >>>> >>>> The tests are looking for a xsd:long in the generated wadl and I took >>>> a look at it and there are only xsd:int generated. I suspect this >>>> might be a jaxb version issue? Should I enable jaxb 2.2 profile to >>>> build this project?
