You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@river.apache.org by "Mark Brouwer (JIRA)" <ji...@apache.org> on 2008/02/24 21:31:14 UTC
[jira] Commented: (RIVER-272) ClassDep.java relies on Sun specific
Internal JDK API
[ https://issues.apache.org/jira/browse/RIVER-272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12571949#action_12571949 ]
Mark Brouwer commented on RIVER-272:
------------------------------------
It is indeed unfortunate that {{ClassDep}} relies on Sun specific JVM classes, which might be removed in the future. It is possible to solve this problem by using a byte code analysis library such as [ASM|http://asm.objectweb.org/], some experimentation indicates that by relying on a 42 KBytes JAR file (licensed under a BSD type license) {{ClassDep}} can be made JVM implementation independent while solving some other outstanding issues as well.
> ClassDep.java relies on Sun specific Internal JDK API
> ------------------------------------------------------
>
> Key: RIVER-272
> URL: https://issues.apache.org/jira/browse/RIVER-272
> Project: River
> Issue Type: Improvement
> Components: com_sun_jini_tool
> Affects Versions: jtsk_2.1
> Environment: Windows XP, JDK 1.4 - JDK 1.6, Eclipse 3.3 IDE
> Reporter: Hakan Kocakulak
>
> ClassDep.java relies on Sun specific Internal JDK API
> import sun.tools.java.BinaryClass;
> > import sun.tools.java.ClassDeclaration; import
> > sun.tools.java.ClassFile; import sun.tools.java.ClassNotFound; import
> > sun.tools.java.ClassPath; import sun.tools.java.Constants; import
> > sun.tools.java.Environment; import sun.tools.java.Identifier; import
> > sun.tools.java.MemberDefinition; import sun.tools.java.Package; import
> > sun.tools.java.Type;
> while building from eclipse IDE, IDE do not add these Classes to classpath and can not build project.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.