Re: GWT compiling tools: is there any way to get the graph of inherited modules? Even a simple flat list would be fine :-)

I've patched the original file in order to provide

• better exit status handling
  
• alternative output type (a textual representation of the deps tree)
  
• possibility to write on the standard output

Follows an excerpt from the dependency tree 

--+com.google.gwt.user.UserAgent                     

  |                                                  

  `--+com.google.gwt.useragent.UserAgent             

     |                                               

     +--+com.google.gwt.core.CoreWithUserAgent       

     |  |                                            

     |  +--+com.google.gwt.core.EmulateJsStack       

     |  |                                            

     |  `-->com.google.gwt.core.CompilerParameters   

     |                                               

     `--+com.google.gwt.emul.EmulationWithUserAgent  

        |                                            

        `--+com.google.gwt.emul.Emulation            

           |                                         

           `-->com.google.gwt.logging.LogImpl        

It works quite fine for me (integrated it into a gradle script) and I'd like to propose a patch, but I've never used gerrit, so I don't know how to propose a new patch to the existing review. May I post the changed file here?

Cheers

Davide

On Tuesday, February 25, 2014 3:31:28 PM UTC+1, Thomas Broyer wrote:

On Tuesday, February 25, 2014 3:25:47 PM UTC+1, Davide Cavestro wrote:

Hi all,

I am in the process of switching linker to Cross-Site-Iframe in order to obtain the compatibility with superdevmode, so I'd like to locate and remove the script tags from the modules I'm inheriting from (since this linker doesn't support them).

Now I'm just  wondering if there's an easy way to obtain from the gwt compiler or other tools the graph of inherited modules (possibly transitive).

It would be really useful in order to avoid having to manually read every inherited module to find additional inherited modules and so on.

Also, having a clear graph of this kind of dependencies would be a good check tool especially when you depend on 3rd party modules.

I once wrote a tiny tool that does just that: https://gwt-review.googlesource.com/1210

Or you could just compile with -logLevel DEBUG and grep for "Loading inherited module" 

--
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/groups/opt_out.