But i cannot limit this in the production rite.. i can limit it during my
development.I have used collapse-all-properties/ which had resolved my
issue and there is only one permutation happening.But i want to know will
there be any disadvantages or any side effects by using it.
On Wednesday,
Right, for production you should not do this, but then in production
mode you will not need superdev.
(Once the extend superdev to deal with this situation you can use
superdev for both compilations)
It helps if you use different gwt.xml files for production and dev (they
could share a
Hi Robert,
i m facing the same issue. can you please tell me what has fixed
your issue.
My compilation-mappings.txt contains
B5079040E7FF0E555046C1AD8B647A66.cache.js
locale en_EN
user.agent gecko1_8
B5079040E7FF0E555046C1AD8B647A66.cache.js
locale en_EN
user.agent ie10
Balázs, the js.embedded.properties configuration property might help here.
Try adding
extend-configuration-property name=js.embedded.properties
value=my.platform /
to your gwt.xml file
On Tue, May 5, 2015 at 6:26 AM, Kishore Palakollu
kishorepalako...@gmail.com wrote:
Hi Robert,
Limit your permutations by being more stringent, e.g. set-property
name=user.agent value=safari /
On May 5, 2015 3:26:56 PM GMT+02:00, Kishore Palakollu
kishorepalako...@gmail.com wrote:
Hi Robert,
i m facing the same issue. can you please tell me what has fixed
your issue.
My
I see others note the Dev Mode On / Off cause this - what's the new
approach then to enter Super Dev Mode?
On Thursday, 4 December 2014 16:49:56 UTC+2, Daniel Kurka wrote:
I am really curious why this is not working for you in the first place.
Since the code we added to SDM should always
OK - this is very confusing, I went back to the Release Notes to see if I
missed a breaking change in this area, but the 2.7.0RC1 release notes still
reference the bookmarklets:
*The Dev Mode On bookmarklet dialog shows whether Super Dev Mode is turned
on for each module on the page.*
And
I'm really not surprise people are hitting this issue. It's not clear (or
wasn't to me) from the Release Notes that you no longer run Super Dev Mode
from the standalone program in 2.7 as was done in 2.6, but that running via
Dev Mode enables it.
Reading the docs on Debugging, they do kind of
On Friday, December 5, 2014 10:00:59 AM UTC+1, Rob Walker wrote:
I'm really not surprise people are hitting this issue. It's not clear (or
wasn't to me) from the Release Notes that you no longer run Super Dev Mode
from the standalone program in 2.7 as was done in 2.6, but that running via
OK, so after a bit of a battle, I can get Dev Mode to run under 2.7, which
now of course launches Super Dev Mode
I needed to change some things though. Our original launch command looked
like this:
ava -cp *%TAS_HOME%/proj/webui/src/com/ascert/webui/vt*;
Sadly the -launcherDir won't work for us I don't think - we're running an
embedded Felix/OSGi server which serves up our application from bundle
JARS. So there is no dir we can point them at.
As per thread below, I think I am making progress with Dev Mode launch
though - at least it is
Nope - even though Dev Mode runs now and goes into Super Dev Mode, our
application is not actually loading in SDM when we visit the web page.
Our web serving and resources are bundled into JARs, so I suspect the idea
of overwriting the .nocache.js is just flawed or not working for this mode.
Hi Rob,
I'm using Jboss Fuse which uses Felix and it works fine in SuperDevMode.
But did I read it right that you start the osgi container embedded with
superdevmode ? I would love to know how I can achieve that as well because
then I don't need to use the -noserver parameter anymore.
I am using
In fact - it does seem to work in both models, but only with the following:
- I have to use the Dev Mod On bookmarklet to trigger a recompile. If I
just reload, it doesn't seem to detect and recompile on it's own. I have a
feeling running SDM directly did do a recompile on reload on
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,
I confirm, I just add GXT to one of my test project and I'm not able to use
sdm anymore:
[ERROR] Current binding properties are expanding to more than one
permutation but per-file compilation requires that each compile operate on
only one permutation.
On Wed, Oct 1, 2014 at 2:34 AM,
We have a short list of issues that have to be addressed before 2.7 RC, and
this is on the list.
On Wed, Oct 1, 2014 at 1:13 AM, Julien Dramaix julien.dram...@gmail.com
wrote:
I confirm, I just add GXT to one of my test project and I'm not able to
use sdm anymore:
[ERROR] Current
I can explain what's going here I think.
Incremental compile is made possible by storing and reusing data in a new
object called a MinimalRebuildCache. Since some of the analysis that
incremental compilation is much simpler when there is only one permutation
being compiled and since the contents
The 'test runner' in this case is just the name of a regular module file,
which happens to be used for running lots of tests, most of which look like
EntryPoints. Nothing too magic going on here, and I've gotten this error by
running modules for more 'normal' gwt apps as well, typically when I
28 matches
Mail list logo
