United StatesChange Country, Oracle Worldwide Web Sites Communities I am a... I want to...
Bug ID: JDK-6981791 remove experimental code for JSR 292
JDK-6981791 : remove experimental code for JSR 292

Details
Type:
Bug
Submit Date:
2010-09-02
Status:
Closed
Updated Date:
2012-02-01
Project Name:
JDK
Resolved Date:
2011-04-25
Component:
hotspot
OS:
generic
Sub-Component:
compiler
CPU:
generic
Priority:
P3
Resolution:
Fixed
Affected Versions:
hs21,7
Fixed Versions:
hs21 (b09)

Related Reports
Backport:
Duplicate:
Relates:
Relates:
Relates:
Relates:
Relates:
Relates:
Relates:

Sub Tasks

Description
This is a tracking bug.  There may be code left from the EDR phase of JSR 292 which is no longer relevant to the final specification.  This code should be removed if no longer relevant, or relegated to some special experimental category.

Features to remove from langtools, hotspot, and jdk include:

- allowTransitionalJSR292 flag (various places)
- deprecated methods
- registerBootstrapMethod and related "Global BSM" functionality

                                    

Comments
EVALUATION

yes
                                     
2010-09-14
EVALUATION

This is the cleanup for a complex 2-phase commit changing a package name from java.dyn to java.lang.invoke, in the JDK, JVM, and langtools.

Here's the approximate timeline:

b130: 7017414 in langtools: Release javac which supports both java.dyn and java.lang.invoke.

b135: 6839872/7012648 in JVM: Release JVM which supports both java.dyn and java.lang.invoke.

b136: 6839872/7012648 in JDK: Release JDK which uses only java.lang.invoke.

b137 (or later): 6981791 (this bug) in JVM and 7028405 in langtools: Release cleaned-up JVM and javac, purging all java.dyn references.


More explanation:

We can't remove transitional code (for java.dyn) in the JVM until the meth-rename-7012648 change (java.lang.invoke) in the JDK works out (into b136 or b137).

If we yank JVM support for java.dyn while the b135 JDK code is alive, we'll get lots more failures.

This assumes that the bulk of testing (in various phases) is using the released build.  If this is so, we can only cut support from the JVM and javac after the new JDK has released.  And of course, we could not release the new JDK until the transitional JVM and javac were released (b135 and b130).
                                     
2011-03-12
EVALUATION

http://hg.openjdk.java.net/jdk7/hotspot-comp/hotspot/rev/ed69575596ac
                                     
2011-04-08



Hardware and Software, Engineered to Work Together