Instead of hard-coding gcj in the spec file, use the "alternatives" feature. I'm attaching a patch for the spec file which changes two lines: The path to the JDK, and the BuildRequires for the JDK version. These reduce the specificity to allow use of Sun and other Java suppliers. An additional upstream issue is that the JNI headers are located with a find command that fails to find all include subdirectories, due to the use of symbolic links. I've just raised this issue on the subversion-devel mailing list to get upstream input. I'll append more info on that once the developers respond.
Created attachment 122983 [details] Reduces specification of JDK allowing alternative suppliers
My post to the subversion-devel list about the JNI headers issue: http://permalink.gmane.org/gmane.comp.version-control.subversion.devel/71849 No response at this time.
I've applied the patch to relax the requirements; thanks.