I will try to extend Java unit test suite in future patches.
On 01/29/2013 07:41 AM, Vladimir Kazanov wrote:I used your patch to the java.el file. It seems fine to me. It made me realize that I don't have any java based integration tests, and thus couldn't test your change easily. This seems like a bit of a hole in the test infrastructure.
I have reformatted/improved the original patch a bit (mostly cosmetic
changes, with one potential bug fixed), and added a fallback value to
the function you mentioned. I knew about the function calculating
relative file names, but it would not make the code cleaner or shorter
The C based integration tests in the 'tests' sbuddirectory in the CEDET repository create C projects, uses srecode to create C code, compile it, parse it with Semantic, etc. I don't know what tools are installed in build bot for CEDET for compiling Java. We'd need to tune anything we develop to that tool chain.