Just to see if I could assist with working out the issue I upgraded my jdk to 1.6.0_35 in ubuntu 10.10 - still same issue.
Must be something else. Anyway I won't bother stuffing around with it any further I can my any cxf patches in my 12.04 On Mon, Oct 1, 2012 at 9:13 PM, Jason Pell <[email protected]> wrote: > So I am having no issues building 2.6.x-fixes on ubuntu 12.04 :-) > > On Mon, Oct 1, 2012 at 8:06 PM, Sergey Beryozkin <[email protected]> wrote: >> Hi Jason >> >> On 01/10/12 03:41, Jason Pell 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? >> >> >> Thanks for actually checking the generated WADLs, I have not seen this issue >> before, so I guess it may be indeed something to do with different JAXB >> implementations. I'll experiment a bit later with jdk 1.6.0_32 >> >> Cheers, Sergey >>
