> It is caused because PostgreSQL, as many other applications such as JDT or CGit, doesn't like a text to contain the null charater (0) .
Why do you say JDT does not like it? The editor, compiler and also the tests work just fine. And I also don't see a problem re: Git. Having said, that, we can probably change this. Please file a bug against JDT Core. Dani From: Mickael Istria <[email protected]> To: [email protected] Date: 10.07.2013 11:20 Subject: [platform-dev] NULL character in MatchingRegionTest confusing JDT, Postgres, cgit... Sent by: [email protected] Hi all, Last I-Build of Platform can build on Jenkins. That's already cool. However, I get an issue with Sonar (and underlying Postgresql) which gets lost with a strange String construct in MatchingRegionsTest. Log of the failure is here: https://hudson.eclipse.org/hudson/job/platform-sonar/9/console . It is caused because PostgreSQL, as many other applications such as JDT or CGit, doesn't like a text to contain the null charater (0) . An example of occurrence can be found at offset 172f in http://git.eclipse.org/c/jdt/eclipse.jdt.core.git/tree/org.eclipse.jdt.core.tests.model/src/org/eclipse/jdt/core/tests/model/MatchingRegionsTest.java . However, test is compiling and working fine because java compilers seem to be OK with having a 0x00 in source code. I'd like to replace this direct inclusion of the null character by a "\0" which should have the same effect at Java execution (in theory) without confusing other apps that directly read source, Would such a change make sense? Cheers, -- Mickael Istria Eclipse developer at JBoss, by Red Hat My blog - My Tweets_______________________________________________ platform-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/platform-dev
_______________________________________________ platform-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/platform-dev
