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

[Davide Cavestro]

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.

[Thomas Broyer]

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" 

[Jens]

Not officially I think, but in GWT's code review tool there is a patch lingering around for a long time: https://gwt-review.googlesource.com/#/c/1210/

Not sure if it needs a little love again to work with GWT 2.6 but its probably a good starting point.

-- J.

[Srini v]

We have an issue similar to it where we want to move to xsi frame linker but what if you have third party dependent modules which have script tag in their module XML. Did anyone face the same issue and solved it?

--
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-tool...@googlegroups.com.
To post to this group, send email to google-we...@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.

[Davide Cavestro]

I've seen that SmartGWT provided the NoScript flavour for their modules, i.e. instead of inheriting from SmartGwt you inherit from SmartGwtNoScript.

I've seen also adding 

<set-configuration-property name='xsiframe.failIfScriptTag' value='FALSE'/>

to your .gwt.xml file works (as suggested by the compiler).

--
You received this message because you are subscribed to a topic in the Google Groups "Google Web Toolkit" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/google-web-toolkit/QLdcqcXXMtk/unsubscribe.
To unsubscribe from this group and all its topics, send an email to google-web-tool...@googlegroups.com.

[Davide Cavestro]

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

[Thomas Broyer]

On Thursday, February 27, 2014 6:20:27 PM UTC+1, Davide Cavestro wrote:

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?

Feel free to post it as a GitHub Gist (or wherever you like), but you could also quite easily update the review in Gerrit.

First create an account in Gerrit, sign the CLA, clone the repo, and setup the commit hook: https://gerrit-review.googlesource.com/Documentation/intro-quick.html

Then you could checkout my review (you'll find the git command in the "download" menu in the upper right in Gerrit), amend the commit (make sure you keep the Change-Id line in the commit message) and then "git push origin HEAD:refs/for/master". The review will be matched by the Change-Id.

Feel free to ask if you need some help setting everything up.