Details
-
Type:
Improvement
-
Status:
In Progress
-
Priority:
Minor
-
Resolution: Unresolved
-
Affects Version/s: None
-
Fix Version/s: 3.1.3
-
Component/s: Runtime: Class Library: GNU Classpath
-
Labels:None
-
Number of attachments :
Description
JikesRVM maintains its own versions of a few classes, such as java.lang.reflect.Constructor. On implementing the JMX extensions, I noticed that some of the method signatures have fallen behind those in Classpath and the Java API. For example, many now take variable arguments where JikesRVM's version still expects an Object array. Maybe we should also setup a JAPI run against the JikesRVM version of the API to catch such things?
Ideally we want to stop having Jikes RVM copies of classes. This may mean we need to refactor code in Classpath to use VM interfaces to things (rather than assuming a native implementation). We should probably do this across the board, even for things like java.lang.Class.