Hasan says that without the change, there are problems with character encodings (e.g. for umlauts) with the JSON MBW. With his fix the problem is resolved (and all tests pass) on our machines. We can not recreate the problem that appears on the build server and have to speculate about the issue. It seems to be some character encoding related problem. I made an additional change and I'll await the next Jenkins build.
However if the problem persists, it would probably be better to keep the changes but disable the failing tests until after release. The problem only appear in some specific environment. Without the change umlauts and similar characters can not be written correctly in any environment. On a related note: who has access to the Jenkins server? Is there some way to run tests/builds manually on the server or in an identical environment for testing this issue? On 30 January 2012 13:14, Reto Bachmann-Gmür <[email protected]> wrote: > Thanks for investigating this. As afaict the change is not release critical > I would suggest to temporarily rollback that pach if it cannot easily be > fixed. > > Cheers, > Reto > On Jan 30, 2012 12:50 PM, "Daniel Spicar" <[email protected]> > wrote: > > > Hmm, it seems the failing builds have no relation to CLEREZZA-670. It > seems > > to be connected to a change by hasan on January 18. > > > > On 28 January 2012 16:42, Daniel Spicar <[email protected]> > wrote: > > > > > Hi Reto. > > > > > > It seems that since the patch CLEREZZA-670 has been applied the tests > in > > > JAX-RS utilities fail on tests with umlauts. I am still trying to > > re-create > > > the problem. That's a thing we should fix for the RC. I will try do do > > that > > > ASAP. > > > > > > Best, > > > Daniel > > > > > > On 28 January 2012 12:18, Reto Bachmann-Gmür <[email protected]> wrote: > > > > > >> Hello > > >> > > >> I just resolved CLEREZZA-679. This should make sure that future > release > > >> candaidates will have the correct year in he copyright of the notice > > file. > > >> Also as component with default NOTICE file have no longer a NOTICE in > > >> subversion this makes it easier to look at the one with an actual > > content. > > >> > > >> The source-release assembly has been modified so that the root > directory > > >> of > > >> each component has the generated notice file. > > >> > > >> If no one complains I will present the next release candidate on > monday > > >> for > > >> vote. From my side the only change since the last relase candidate > have > > >> been licensing and packaging issues. > > >> > > >> Cheers, > > >> Reto > > >> > > > > > > > > >
