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
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
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
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
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.
--
You received this message
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?
On Tuesday, 25 February 2014, Jens jens.nehlme...@gmail.com wrote:
Not officially
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
