javacomp vs testing Java 1.5 features

[Di-an JAN]

Currently, the testsuite uses ``javacomp.sh'' from gnulib to compile Java
parsers, which is configured by ``configure.ac'' for Java 1.3 sources.
This serves as a check that the generated parsers does not use newer
language features, but does not allow testing support for Java 1.5
features.

I'm not familiar with autoconf, but I'm thinking

1. Use a separate configure to create a javacomp15.sh.

2. Change javacomp.m4 in gnulib to allow generating javacomp15.sh, etc.

3. Change javacomp.sh.in in gnulib to allow different source versions.
   Problem is that if configure found, say, gcj 3.4 and javac 1.5,
   then javacomp.sh would be configured for gcj 3.4, which cannot handle
   1.5 sources.  Simple solution: set JAVAC on configure.
   Or store in javacomp.sh config. info on all compilers found when not
   using JAVAC.

4. Use javacomp.c from gnulib to create a standalone program that does
   the compiler detection at runtime.  Not efficient as it may have to
   run various compilers mutiple times to check configuration for EACH
   compile request.

Ideas?

Di-an Jan