Also just hit the same issue in 2.7.0
Using the -noincremental SDM option seems to get around it, I'd presume
though at the expense of recompile speed.
On Tuesday, 25 November 2014 16:25:04 UTC+2, Alexander Tarasov wrote:
As I can see in gwt 2.7.0 release it was not fixed.
Hello John,
could you please clarify if the issue was fixed or not? I have have the
same error in 2.7. Is it related to gxt or not?
среда, 1 октября 2014 г., 23:08:31 UTC+2 пользователь John Stalcup написал:
We have a short list of issues that have to be addressed before 2.7 RC,
and this
Hi,
Is there a way to see which properties cause the permutations?
(I'm using GWT 2.7.0)
best, Robert
On Tuesday, September 30, 2014 8:53:22 PM UTC+2, John Stalcup wrote:
I can explain what's going here I think.
Incremental compile is made possible by storing and reusing data in a new
On Thursday, December 4, 2014 10:15:36 AM UTC+1, Robert Hoffmann wrote:
Hi,
Is there a way to see which properties cause the permutations?
(I'm using GWT 2.7.0)
When compiling your project, you should have a compilation-mappings.txt
file generated next to the *.nocache.js.
--
You
Is it ok?
9E2D25ADAB9D44AFEFC3E887DE3E3116.cache.js
gxt.user.agent chrome
user.agent safari
user.agent.os linux
9E2D25ADAB9D44AFEFC3E887DE3E3116.cache.js
gxt.user.agent chrome
user.agent safari
user.agent.os mac
9E2D25ADAB9D44AFEFC3E887DE3E3116.cache.js
gxt.user.agent chrome
user.agent safari
@thomas
thank you, that helped me to reduce the permutations to one.
For the record, compilation-mappings.txt contained multiple cache.js
file entries, now it only contains one
FC8BCE744D2BA8E0C463CE0D2F389DB7.cache.js
Devmode:devmode.js
...and now sdm works.
And it's fast :-)
On
I'm seeing this file in the artefacts generated by the SDM compile in the
temp dir. Isn't editing this file only going to apply to the current
invocation though?
Presumably next time around it's going to get a different temp dir, and
this fill will get recreated again.
Have to confess - I
The mappings file only reports what was going on in the compile phase,
so modifying it has no effect.
You have to set specific values for your properties in the module.xml files:
e.g.
set-property name=user.agent value=safari/
SDM picks this change up I believe without restart. However
OK - I know I'm being exceptionally dumb here, but won't that also limit a
production build to that 1 permutation?
On Thursday, 4 December 2014 16:06:23 UTC+2, Robert Hoffmann wrote:
The mappings file only reports what was going on in the compile phase,
so modifying it has no effect.
You
I am really curious why this is not working for you in the first place.
Since the code we added to SDM should always scope you down to one
permutation. Are you still using bookmarklets? (These do not deal with this
properly and should not be used anymore).
On Thu, Dec 4, 2014 at 3:43 PM, Rob
It would. So I have a common.gwt.xml which a Dev.gwt.xml inherits and
restricts (as discussed in this topic).
The production.gwt.xml also inherits from common but without restrictions.
In such or similar setup you can also keep other dev specific stuff separated,
logging etc.
On December 4,
11 matches
Mail list logo
