[
https://issues.apache.org/jira/browse/RIVER-272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Peter Firmstone updated RIVER-272:
----------------------------------
Attachment: ClassDep-a5.patch
Add more functionality and corrections
The following options remain to be implemented:
-outer
By default, if a static nested class is included in the dependency graph,
all references from that static nested class to its immediate lexically
enclosing class are ignored (except when the static nested class extends its
outer class), to avoid inadvertent inclusion of the enclosing class. (The
default is chosen this way because the compiled class file of a static nested
class always contains a reference to the immediate lexically enclosing class.)
This option causes all such references to be considered rather than ignored.
Note that this option is needed very infrequently.
-edges
By default, the classes which are included in the dependency graph are
displayed in the output. This option specifies that instead, the classes which
are excluded from the dependency graph, but which are directly referenced by
classes in the dependency graph, should be displayed in the output. These
classes form the outside "edges" of the dependency graph.
For example, you might exclude classes from the Java 2 SDK from the
dependency graph because you don't want to include them in your JAR file, but
you might be interested in knowing which classes from the Java 2 SDK are
referenced directly by the classes in your JAR file. The -edges option can be
used to display this information.
-tell class
Specifies the fully qualified name of a class for which dependency
information is desired. This option causes the tool to display information
about every class in the dependency graph that references the specified class.
This information is sent to the error stream of the tool, not to the normal
output stream. This option can be specified zero or more times. If this option
is used, all other output options are ignored, and the normal class output is
not produced. This option is useful for debugging.
More to come.
Cheers,
Peter.
> 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
> Attachments: ClassDep-a4.patch, ClassDep-a5.patch, classdepend.zip,
> classdepend_backport.tgz, ClassDepReplacement.tgz,
> ClassDepReplacement_alpha-2.tgz, ClassDepReplacement_alpha-3.tgz,
> ClassDepReplacement_alpha-4.tgz
>
>
> 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.
