Last night I wrote a quick one-off javac-based tool to parse and analyze
all of GWT's source code, and to extract out inter-file dependencies (e.g.,
dev/core/src/com/google/gwt/dev/GWTShell.java depends on
dev/core/src/com/google/gwt/dev/cfg/ModuleDef.java). I then ran a
strongly-connected
Interesting work. For an interactive solution you may try IntelliJ's DSM
analysis: http://www.jetbrains.com/idea/features/dependency_analysis.html
After getting used to it, it gives pretty good information about
dependencies. Maybe it also knows about JSNI dependencies.
-- J.
--
I do care a lot about this topic:
I'm new to the source code of GWT; I did started digging into it less than
one month ago with the intent of ease use of GWT in OSGi environment.
For this reason, I did a (simple) run of JDepend on the GWT source code,
merged all together in a single project, to
sounds *very* promising
On Fri, Nov 15, 2013 at 11:56 AM, Matthew Dempsky mdemp...@google.comwrote:
Last night I wrote a quick one-off javac-based tool to parse and analyze
all of GWT's source code, and to extract out inter-file dependencies (e.g.,
On Fri, Nov 15, 2013 at 11:56 AM, Matthew Dempsky mdemp...@google.comwrote:
If I first collapse all source files into a single vertex, then our 502
packages still form 394 SCCs.
Oops, that should be collapse all source files *within a Java package*
into a single vertex. (Collapsing all
