I think Alain's use case is a legit one, and the SmartGWT product probably
also lives in that world to an extent - let the user write Java that mostly
interacts with JS libraries, and let them worry about which browser is
running, but compile the code to run anywhere. I can't speak to their
'older
, Goktug Gokdogan wrote:
On Mon, Jun 30, 2014 at 8:46 PM, Colin Alworth nilo...@gmail.com
javascript: wrote:
Sounds great, but is there a reason that we're now starting at IE9+ and
not IE10+, thus giving us typed arrays, web workers, web sockets, etc? I
only ask because the kind of case
PotentialElement seems to be one of those ghost features that was never
finished, or at least never correctly documented, so might as well be half
done:
EXPERIMENTAL and subject to change. Do not use this in production code.
We've never used it, and I've only encouraged people to stay away from
Sounds great, but is there a reason that we're now starting at IE9+ and not
IE10+, thus giving us typed arrays, web workers, web sockets, etc? I only
ask because the kind of case where you are giving up User (and Widget, RPC,
Timer, and other fairly high-level apis) seems to suggest that you
in
the root directory, then simply compiling user tests, I get a failure:
[colin@modo user (master)]$ ant clean compile.tests
Buildfile: /Users/colin/Documents/idea/gwt/user/build.xml
clean:
[delete] Deleting directory
/Users/colin/Documents/idea/gwt/build/out/user
compile.dev.tests
With some help from Jens Nehlmeier over in ##gwt, it looks like there are
two distinct issues preventing the build from passing presently The first
is that the class ImmediateCompileFails does in fact cause problems with
compiling - the simplest fix was to tell the compile.tests target to leave
:
On Tuesday, June 10, 2014 12:33:40 AM UTC+2, Colin Alworth wrote:
Currently SafeHtml co live in gwt-user, though they are for the most
part listed in a shared package, implying that a server can use them.
However, gwt-user.jar also includes javax packages as well as hibernate,
w3c, etc
, but presently
isn't possible for the majority of GWT backends.
Ideas on why it is the way it is? Thoughts on how to make it available to
the server (without giving it yet another jar a la requestfactory-server)?
Interest in a contributed SafeHtmlTemplates implementation for JVM?
Thanks,
Colin
AutoBeanFactorySource also made it in there) - does that
seem like a reasonable step?
On Mon, Jun 9, 2014 at 6:22 PM, John A. Tamplin j...@jaet.org wrote:
On Mon, Jun 9, 2014 at 6:33 PM, Colin Alworth niloc...@gmail.com wrote:
Currently SafeHtml co live in gwt-user, though they are for the most
part
I've just opened https://gwt-review.googlesource.com/7780 to make it
possible to specify a fallback for any/all useragents that don't match one
of the built-in rules, via a rule like:
set-property-fallback name=user.agent value=webkit/
This example rule treats any unknown useragent as if
Sorry, that first line should say 'safari' (or any other valid user.agent
value), not 'webkit'. Wishful thinking perhaps...
set-property-fallback name=user.agent value=*safari*/
--
You received this message because you are subscribed to the Google Groups GWT
Contributors group.
To unsubscribe
This seems to be a pretty quiet discussion so far, with mostly Zied
responding to himself and Thomas’s one initial reply, but it is a holiday
weekend here in the US, so that might be contributing to the lack of
additional responses. I haven’t had the chance to even look at the initial
proposal
Create a Viewer that will give you a static look at how the currently open
UIBinder page you are working on would look in a browser. I find this would
be useful because if you are working on a page that you have to navigate
through a lot of stuff to get to on your website just to look at your
Only note to add here is that the AngularJS project does require a CLA also
(see https://github.com/angular/angular.js/blob/master/CONTRIBUTING.md#cla)
- it looks like they either have a bot which complains about missing CLAs
on file (and so some associated between username and real name), or a
Jens is dead on - several API changes from 2.4/2.5 to 2.6 make it difficult
for a library to stradle that divide. We'll be shipping a GXT 3.1 beta Real
Soon Now to enable users to switch to GWT 2.6. Breaking changes include:
- Changing permutations (ie6 and opera are gone, ie10 was added,
There is a prototype project enabling Eclipse to debug the JS running in
the browser with sourcemaps - check it out at http://github.com/sdbg/sdbg.
On Thursday, November 15, 2012 8:46:26 AM UTC-8, Clint Gilbert wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
If I could hook Eclipse
In CrossSiteIframeTemplate.js this is handled by assigning
__MODULE_FUNC__.__softPermutationId to 0 to begin with, and then only
change that value if : was present in the permutation string. I'm not
seeing any other js files that init __softPermutationId to 0, and only
permutations.js assigns
code or the running app, it is hard to be more specific.
On Sat, Feb 8, 2014 at 11:50 PM, Vassilis Virvilis vasv...@gmail.comwrote:
Hi Colin,
The problem is when DevMod is off. As I said when when DevMod is on (with
compile) everything works in all browsers. However when I am not developing
I
Just watched https://gwt-review.googlesource.com/#/c/6342/ wander by, but
I've also seen this trying to understand the general compiler changes that
are happening in trunk gwt - is the CompilerContext really an essential
part of ModuleDefLoader in general? From what I can see it is tracked as a
:
On Mon, Feb 10, 2014 at 2:57 PM, Colin Alworth nilo...@gmail.comjavascript:
wrote:
Just watched https://gwt-review.googlesource.com/#/c/6342/ wander by,
but I've also seen this trying to understand the general compiler changes
that are happening in trunk gwt - is the CompilerContext really
Can you confirm that you are hitting the Compile button in each browser and
that the SDM console is indicating that it is recompiling for each other
user agent? It sounds as though you might be compiling when you start up
one browser, then just turning dev mode on without recompiling in other
There have been a few quick discussions about this in ##gwt on irc, and
while I think we probably need to both move this to -contrib before much
longer but also get some of the compiler experts involved, I suspect this
is going to end up being a specific tool to optimize sufficiently c-like
If you know enough to start writing generators, it almost certainly is not
a concern - you are probably also careful with which GWT version you are
using as well as which gwt-m-p version. A problem can occur if more than
one version of gwt-dev is present on the classpath, such as a mistakenly
For JSON, you'd have go pretty far out of your way to get attacked, like
loading something untrusted via JSONP, or manually parsing your own json
with eval (rather than any of the safe built-in tools), or, ya know,
forgetting to run SSL and having someone intercept your server
communication.
The concern I've heard expressed during in-person discussions about how to
do this is that a written document of answers 'feels' more real and
concrete than a group of people answer questions live, since they clearly
have no chance to vet their answers from their own organization or with
each
Another set of dangerous code to look for would be any SafeHtmlUtils or
SafeHtmlBuilder (and their uri/style conterparts) call that should take
'constant' or 'trusted' but instead takes untrusted user data. Custom
implementions of SafeHtml should also be treated as suspect.
These all fall
Something funny has happened to the dont-reload-the-page code on
gwtproject.org, but I'm not seeing any obvious commit that should have done
this.
Steps to repro:
1) visit http://gwtproject.org/, or any *top level* document
2) observe that any link you hover looks to be correct, and visiting
Another thought: Christian Sedilek, Dan Kurka, and myself can also be found
pretty frequently in ##gwt on irc.freenode.net for a more informal
discussion - I'd love to see more steering committee members hang out
there, even if just idling most of the time, and chatting once in a while.
This system property isn't listed when either dev mode or the compiler runs
because it is a system property, not a program arg. It should be provided
with the other VM args when you start Java. These aren't listed as part of
the normal properties, but are documented here:
:
It seems that we need to build the release with -sourceLevel 6 for it to
work with Java 6.
On Thu, Dec 5, 2013 at 10:43 PM, Colin Alworth nilo...@gmail.comjavascript:
wrote:
Sorry for being unclear - I'm building/testing an application that makes
use of GWT while still on Java6, not building
I'm still running into trouble with the major version of the compiled
classes being 51, so I'm unable to gwt 2.6.0-rc3 to work under jdk 1.6. As
before, I was able to confirm that the actual .class files are compiled
correctly, but yet I get fatal errors in attempting to run dev mode.
Testing
/gwt/user/src/com/google/gwt/core/client/Duration.javat
fileNameq
fileNameq
On Friday, December 6, 2013 12:10:10 AM UTC-6, Roberto Lublinerman wrote:
Hi Colin,
Did you do ant clean? I find it strange that the resource points to
Matthew's hard drive, as if Impl was precompiled by him
or by
just forgetting to call some cleanup method. It may also be that if you
write this same code in pure JS, there will be a leak and that you cannot
do anything about it.
On Wednesday, December 4, 2013 12:21:23 PM UTC-6, ak...@ualberta.net wrote:
Hi Colin,
https://lh4.googleusercontent.com
Can you try compiling in PRETTY? This will make the retaining tree graph in
chrome's inspector easier to tell where things are coming from and what is
tracking them. But at a glance, something registered something with
google.visualization, and didn't unregister it. Knowing what gD, iv, and fv
,
shouldn't it be dropped from 2.6 before it goes final?
Aside from that, seems to be passing all our smoke tests so far, will have
more comprehensive results tomorrow.
-Colin
On Monday, December 2, 2013 4:49:29 PM UTC-6, Matthew Dempsky wrote:
I cut a new 2.6.0 release candidate this morning
Just to confirm, the plan is to set this in master as well as releases/2.6,
and this will go out in 2.6.0-rc2?
--
http://groups.google.com/group/Google-Web-Toolkit-Contributors
---
You received this message because you are subscribed to the Google Groups GWT
Contributors group.
To unsubscribe
that Carlos mentioned, launching FF as root.
On Saturday, November 9, 2013 9:52:55 PM UTC-7, Carlos Aguayo wrote:
I really appreciate your help Colin.
At this point I believe it's some misconfiguration in my computer. I
tried to do a jconsole on the devmode process and it said it couldn't
There is a workaround - I'm on my phone now, but I posted it in the bug
report. Essentially you can tell the plugin to not worry about invalid
SDKs, and either mark then as merely errors, or just ignore it entirely.
With that set, we've noticed no other I'll effects so far.
On Nov 17, 2013 12:29
We're using this at Sencha with pretty good success, though it really is
designed to be for testing applications, not libraries. I know of a few GXT
customers who are using it with gxt-driver for widget support, but it is
still pretty early - either everyone thinks it works out great, or there
None of the WEB-INF/ directory should be needed, provided you are not
running a servlet container, but that is the only 'server-only' code that
generally is created that will take up any meaningful size.
Another option at your disposal is to get rid of the permutations and
instead make just
Another new toy to propose for saner Selenium testing:
https://github.com/niloc132/gwt-driver
On Monday, November 11, 2013 8:59:49 AM UTC-6, Ed wrote:
If you search the forum well, you will find all you need.. Example:
the 'memory leak' one.
On Saturday, November 9, 2013 11:01:40 AM UTC-6, Carlos Aguayo wrote:
Thanks Colin, yeah that's what I figured, initially I thought that it
would be a problem in the plugin given that it was only blocking Firefox
and only in OS X (given that Chrome worked and also Firefox
By default, Selenium starts the browser with a fresh profile every time,
which means that it has no plugins installed. On quitting, it deletes that
profile again, to make sure that it won't slowly consume your disk.
When you start the firefox driver instance, you can ask it to load profile
, at 17:47, Colin Alworth niloc...@gmail.com wrote:
Thanks Roberto, I'll give that a shot. I normally work with Java 7, but we
want our code to work with anyone who chooses to use Java 6 as well - and I
surmised that GWT had the same goal.
Would it make sense to consider a warning indicating
Line 155:
ssize_t n = recv(sock, readBuf, BUF_SIZE, 0);
That seems to say 'block until bytes are written by the other end of the
socket', or in other words, wait until the JVM is ready to go. Are you sure
that the IDE isn't paused on a breakpoint, or that you have waited long
enough for the
I'm not yet convinced that this isn't either a) a workspace issue or b) a
decision the community reached and I missed, but I figured I should stick
it out there and see if someone can correct me.
I've just brought our project up to date with GWT 2.6.0-rc1 from maven, and
I can verify that the
-500-9148
On Fri, Nov 8, 2013 at 3:31 PM, Colin Alworth nilo...@gmail.comjavascript:
wrote:
I'm not yet convinced that this isn't either a) a workspace issue or b) a
decision the community reached and I missed, but I figured I should stick
it out there and see if someone can correct me
Just moved to eclipse to verify a possible issue with the snapshot (nope,
bug was in my code), and eclipse seems to do okay with finding each
artifact in its own snapshot.
Can you ping the list when you push a new set of snapshots?
-Colin
On Nov 5, 2013 7:55 PM, Matthew Dempsky mdemp
/MojoExecutionException
Error while deploying, ignore errors? (y/N):
I'm going to root cause what's going on, but maybe you have an idea
what's going on?
On Wed, Nov 6, 2013 at 1:49 PM, Colin Alworth niloc...@gmail.comwrote:
Just moved to eclipse to verify a possible issue with the snapshot
(nope, bug
. Snapshots are the
other way around, you are allowed to update snapshots, as well as remove
stale ones.
On the plus side, the -SNAPSHOT build looks to be working great from my
testing.
On Wed, Nov 6, 2013 at 7:07 PM, Matthew Dempsky mdemp...@google.com wrote:
On Wed, Nov 6, 2013 at 4:54 PM, Colin
-2.6.0-rc1.zip
(Next up the Maven 2.6.0-rc1 artifacts.)
On Wed, Nov 6, 2013 at 5:07 PM, Matthew Dempsky mdemp...@google.comwrote:
On Wed, Nov 6, 2013 at 4:54 PM, Colin Alworth niloc...@gmail.com wrote:
My vote is 2.6.0-SNAPSHOT and 2.6.0-rc1, in case we need a bug fix
release... Being
It looks like while I can get maven from the command line to get along with
that repo, IntelliJ isn't having it - it is getting confused by the fact
that the latest gwt-user snapshot 2.6.0-20131105.081128-3 only has a
sources jar and a pom, no actual jar with compiled code in it. The -1 jar
is
If you compile in PRETTY instead of DETAILED, it won't intern those
strings, but still will leave the output mostly readable (just no packages).
Without seeing the rest of the structure of the module files, it is hard to
speculate, but we're using more or less the same idea successfully, though
We've found experimentally that the meta tag has no effect on IE8 when in
intranet mode. We've further found that it does seem to respect the http
header, which could be set in a filter like this:
public class LatestIEFilter implements Filter {
@Override
public void doFilter(ServletRequest
=false /
I'll try to build a more complex test case that actually uses the
properties defined, just in case the compiler is getting to clever for me.
On Monday, October 28, 2013 12:45:45 PM UTC-5, Colin Alworth wrote:
If you compile in PRETTY instead of DETAILED, it won't intern those
strings
Chak, take a look again at my post - while the meta tag definitely does not
work to tell IE8 to behave when in intranet mode, loading the exact same
html content and sending the same ua-compat details over a HTTP header
*does* solve this.
On Monday, October 28, 2013 3:08:47 PM UTC-5, Chak Lai
I can't reproduce this, we're also running ant clean elemental dist on our
teamcity build. We're also running ubuntu 12, python 2.7.3. Last confirmed
building as of 0d6a865556ca56840114e8397a1f2be522e83361 (current HEAD).
On Monday, October 28, 2013 5:43:04 AM UTC-5, Jens wrote:
I just tried
:
Thx for checking it, Colin.
Pretty strange that it doesn't work. The error also happens if I just
execute ant on console directly on the server.
-- J.
--
http://groups.google.com/group/Google-Web-Toolkit-Contributors
---
You received this message because you are subscribed to the Google
I've just put up a patch that seems to resolve a current issue in deploying
snapshots to a maven repository: https://gwt-review.googlesource.com/5192
The basis of the problem requiring this patch is that maven (at least maven
3, possibly not maven 2) expects unique snapshots, and that each call
Without specifics of what may be referencing those objects it is hard to
say for sure, but memory details while running in dev mode will likely not
reflect the compiled code. To properly test your memory patterns, compile
to JavaScript with style PRETTY or DETAILED so you can read the code, and
If only *all* of my changes were that easy to make...
On Tuesday, October 22, 2013 8:15:12 AM UTC-5, Andrés Testi wrote:
Thanks Colin! I'm glad to see the power of the community in action :-)
- Andrés Testi
El lunes, 21 de octubre de 2013 19:59:53 UTC-3, Colin Alworth escribió:
Tentative
Amazingly, it still works great in the IE11 preview too! Only gotcha is
that the missing plugin page thinks you are running firefox, so you need to
manually grab the right copy of the IE plugin.
On Tuesday, October 22, 2013 12:58:57 PM UTC-5, Brian Slesinsky wrote:
I expect that by next
I end up debugging IE in dev mode on a regular basis as well, though in a
VM, through to my host OS's Eclipse or IntelliJ debugger. It is
significantly slower than running the IDE and browser on the same OS, but
it does let you set up your env once and debug multiple OSes whenever you
like.
On
Patrick, looking at these, only two appear to have code reviews, and both
are in the pre-git system. Gerrit, the current system, needs a CLA before
it allows changes, to make sure that there are no copyright/licensing
issues with contributions, and makes history/change management a little
Tentative patch up at https://gwt-review.googlesource.com/5063 - can
someone sanity check it for me? It looks like step 4 (now step 3) should
have previously been pointing to step 3 (now step 2), so is now more
correct.
On Sunday, October 20, 2013 2:12:17 PM UTC-5, Andrés Testi wrote:
Thanks
Just wandered by https://gwt-review.googlesource.com/#/c/1040/ and noticed
that with this change, any downstream generator/linker using the static
helper methods in Name will no longer build across 2.5.1 to 2.6.0. With the
other discussions going on about JRE and browser support, perhaps we
or a
servlet/filter/htaccess that can be customized to correct for this in the
git repo, so I'm assuming that this is a server configuration change that
needs to be made. Can someone confirm that, or point me in the right
direction for a change I can make as a contributor?
Thanks,
Colin
--
http
:
/Users/colin/Documents/idea/gwt/build/out/samples/JSON/war/WEB-INF/classes
[gwt.javac] Compiling 1 source file to
/Users/colin/Documents/idea/gwt/build/out/samples/JSON/war/WEB-INF/classes
[gwt.javac]
/Users/colin/Documents/idea/gwt/samples/json/src/com/google/gwt/sample/json/client/JSON.java:132
Its never too late - I don't know how far Julien has gotten, but I've been
distracted by other work, as well as trying to nail down conceptually where
GSS meets ClientBundle.
For my part, SASS or LESS are a major step down from what we already have -
the purpose of GWT in general is to let you
, in ##gwt on freenode, or on the
call tomorrow,
Colin
--
http://groups.google.com/group/Google-Web-Toolkit-Contributors
---
You received this message because you are subscribed to the Google Groups GWT
Contributors group.
To unsubscribe from this group and stop receiving emails from it, send
plugins. However, I believe Firefox 24 will be an ESR
release so I think it's worth rebuilding that version.
On Tue, Sep 24, 2013 at 4:31 PM, Colin Alworth nilo...@gmail.comjavascript:
wrote:
I spent a little time this weekend learning how to build firefox plugins,
and a little time spilled
tried it in FF24/mac so far.
-Colin
On Tuesday, September 24, 2013 8:02:54 PM UTC-5, Brian Slesinsky wrote:
+cromwellian since he did unload support.
Oops, I see now that you attached it. Could you upload it to Gerrit?
I looked pretty hard for a reason why it's window.onUnload
I downloaded and upgrade the tool set to Eclipse4.3/Google/GWT plugin on
Windows 8.
All is good, except the GWT wizards that used to be on the top of the New
menu are gone. What do I need to do to put them back?
--
You received this message because you are subscribed to the Google Groups
I deployed it to Google App Engine here
http://neptune-1.appspot.com/
Note the source code download doesn't have the App Engine artifacts and
some changes with session handling required for App Engine deployment.
--
You received this message because you are subscribed to the Google Groups
A few years back, I did some exploration of using LinkedIn OAuth in GWT
applications. I recently rewrite the sample app with the latest Scribe
library by Fernandez Pablo (https://github.com/fernandezpablo85/scribe-java),
and add a few more LinkedIn api calls. You should be able to use it as a
I've got to second Thomas on this point - adding a new user.agent is very
non-trivial at least without an overhaul of CssResource generation. In GXT
3 we took the route of providing our own PropertyProviderGenerator and
adding a few new user agents (ie7, ie10 for a start), but quickly found
that
for support.
On Tue, Aug 27, 2013 at 3:24 AM, Thomas Broyer
t.br...@gmail.comjavascript:
wrote:
On Tuesday, August 27, 2013 1:42:35 AM UTC+2, Colin Alworth wrote:
I'd be interested in helping with either approach. The phloc-css
project looks interesting if we are only trying to add
special support from GWTTestCase infrastructure. Also,
we are not going have an environment to automate benchmarks written on this
any time soon.
If there is enough demand later, parts of this code can be resurrected to
build a new benchmark system.
Thoughts?
-Colin
--
http
new properties with phloc-css, and create a new ResourcePrototype
(StylesheetResource perhaps?) with its own resource generator to put code
through closure's wringer.
-Colin
On Monday, August 26, 2013 5:38:45 AM UTC-5, Julien Dramaix wrote:
Hi all,
Just to inform you that I would like
I got a tweet from you asking for a donation (or rather a 'partner', which
apparently means 'money'), but couldn't frame a useful response in 140
chars, so since this thread is coming back, I thought to do so here
instead.
What license are you offering these code samples under - if it isn't
Nice writeup. Comments/questions (since comments seem disabled in the docs):
* @Entry looks great - there has been some discussion in IRC about some
way to do this for easier library wrapping code, but every direction we
looked at with JSOs ended up with a little more cruft than we really
Colin Alworth has posted comments on this change.
Change subject: Add interfaces for widgets.
..
Patch Set 8:
What is the thinking for the remaining 10%-ish of widgets - all of the cell
widgets (except CellPanel), remaining
Colin Alworth has posted comments on this change.
Change subject: Ensure clinits get called for JSO instance methods.
..
Patch Set 2:
(1 comment)
File dev/core/src/com
Colin Alworth has posted comments on this change.
Change subject: Ensure clinits get called for JSO instance methods.
..
Patch Set 2:
(2 comments)
File user/test/com
: gwt
Gerrit-Branch: master
Gerrit-Owner: Colin Alworth niloc...@gmail.com
Gerrit-Reviewer: Colin Alworth niloc...@gmail.com
Gerrit-Reviewer: John A. Tamplin j...@jaet.org
Gerrit-Reviewer: Leeroy Jenkins jenk...@gwtproject.org
--
http://groups.google.com/group/Google-Web-Toolkit-Contributors
Colin Alworth has posted comments on this change.
Change subject: Add interfaces for widgets.
..
Patch Set 6:
(4 comments)
File user/src/com/google/gwt/dom/client
Colin Alworth has uploaded a new change for review.
https://gwt-review.googlesource.com/3361
Change subject: Ensure clinits get called for JSO instance methods.
..
Ensure clinits get called for JSO instance methods
Colin Alworth has posted comments on this change.
Change subject: Ensure clinits get called for JSO instance methods.
..
Patch Set 1:
Afraid not, this is the exact same patch we looked at - only difference was
that I pulled
Colin Alworth has posted comments on this change.
Change subject: Add hasClassName method in com.google.gwt.dom.client.Element
..
Patch Set 6: Code-Review+1
Nope, we can work with it - a wrapper isn't really an option, since
Colin Alworth has posted comments on this change.
Change subject: Add hasClassName method in com.google.gwt.dom.client.Element
..
Patch Set 6:
Thanks Goktug - one of the distinct advantages of extending Element is that
we
What are we looking at having in these interfaces? The discussion that
Goktug and I had a few months ago got stalled around the concept that these
interfaces were trying to both be a) implementation independent but also b)
rich enough to be useful. Doing both is hard/meaningless.
To pick an
any internal rebuilding via appearance/cells/etc).
-Colin
On Wed, Jun 5, 2013 at 4:36 PM, Stephen Haberman
step...@exigencecorp.comwrote:
Yeah this Type 1 style is really PITA in the long term, especially if
views are a bit more complex.
I disagree; I actually prefer Type 1. Although to each
Colin Alworth has posted comments on this change.
Change subject: Add hasClassName method in com.google.gwt.dom.client.Element
..
Patch Set 3: Code-Review-1
As an idea, looks good, but remember that JSOs are a particularly
Colin Alworth has posted comments on this change.
Change subject: Use JSON.parse() instead of eval() to deserialize rpc
callback payload
..
Patch Set 1:
(1 comment)
The ServerSerializationStreamWriter will also need
In most cases that is true, but CssResource is an interesting exception.
The fallback rules work by looking to see if there is no implementation for
a particular value, and if not, looking to see if there *is* an
implementation for some other value. In the case of ClientBundle and
On Thu, Mar 21, 2013 at 9:24 PM, Stephen Haberman
step...@exigencecorp.comwrote:
Also we can use this as an opportunity to provide a compatibility
layer across different vendors and/or different widget systems.
I suppose, technically yes. That is more complex than what I really had
in
The problem with this answer is that the failure is silent and surprising
for Java developers, and that the optimizations can make it even more so.
If I recall correctly, calling a static method in the same type from an
instance method is not enough to get the static initializer called - an
, 2013 4:43:13 PM UTC-5, John A. Tamplin wrote:
On Sat, Mar 16, 2013 at 5:30 PM, Colin Alworth nilo...@gmail.comjavascript:
wrote:
The problem with this answer is that the failure is silent and surprising
for Java developers, and that the optimizations can make it even more so.
If I recall
:13:11 PM UTC-5, Colin Alworth wrote:
We've been using the Maven2 emma:emma goal, with no modifications at all
- seems to behave correctly with htmlunit in dev mode, both for traditional
junit tests and GWTTestCases. No changes to the pom, just executing
emma:emma with maven 2.2.1 on our
We've been using the Maven2 emma:emma goal, with no modifications at all -
seems to behave correctly with htmlunit in dev mode, both for traditional
junit tests and GWTTestCases. No changes to the pom, just executing
emma:emma with maven 2.2.1 on our project.
On Thursday, March 7, 2013
301 - 400 of 489 matches
Mail list logo
