FULL PRODUCT VERSION :
java version "1.9.0-ea"
Java(TM) SE Runtime Environment (build 1.9.0-ea-b65)
Java HotSpot(TM) 64-Bit Server VM (build 1.9.0-ea-b65, mixed mode)


ADDITIONAL OS VERSION INFORMATION :
3.13.0-53-generic #89-Ubuntu SMP Wed May 20 10:34:39 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux


A DESCRIPTION OF THE PROBLEM :
When invoking rmic with -Xnew something tries to use javac with no longer supported versions for -source and -target.

This is from one of the testcases of Apache Ant with provides access to -Xnew when the "Xnew" rmic compiler is chosen, see http://ant.apache.org/manual/Tasks/rmic.html

Apart from providing a more meaningful error message, it would be good if you'd explicitly list the -Xnew option as removed inside the release notes.

REGRESSION. Last worked in version 8u45

ADDITIONAL REGRESSION INFORMATION:
java version "1.8.0_45"
Java(TM) SE Runtime Environment (build 1.8.0_45-b14)
Java HotSpot(TM) 64-Bit Server VM (build 25.45-b02, mixed mode)


STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
create a remote class (in my example RemoteTimestampImpl.class) and run

rmic -Xnew -vcompat RemoteTimestampImpl

EXPECTED VERSUS ACTUAL BEHAVIOR :
EXPECTED -
One of two things, either

* either compile _Skel and _Stub classes
* or fail with a message inidicating that -Xnew is no longer supported

ACTUAL -
ant/src/etc/testcases/taskdefs/rmic/src$ /usr/lib/jvm/jdk1.9.0/bin/rmic -Xnew -vcompat RemoteTimestampImpl
error: Source option 1.3 is no longer supported. Use 1.6 or later.
error: Target option 1.1 is no longer supported. Use 1.6 or later.

I certainly haven't specified source or target and there is no way to use a different version.

REPRODUCIBILITY :
This bug can be reproduced always.