to your
production server as possible.
Personally I don't like launching a servlet container via a build tool so I
use a jetty docker container and a shell script to deploy the webapp.
-- J.
Wejden Mrabti schrieb am Mittwoch, 1. Mai 2024 um 17:09:57 UTC+2:
>
> thank you @jens for
I would first focus on upgrading Java, GWT and possibly GXT if it is
incompatible with newest GWT. The DataSource error will go away once you
upgrade GWT because newer GWT versions use a newer Jetty. Keep in mind that
in newest GWT the use of embedded Jetty as appliction server during
A full example for multiple maven modules (more than just three) can be
found here: https://github.com/tbroyer/gwt-maven-plugin/tree/main/src/it/e2e
You have to add gwt-lib to your own maven library
modules that contain a module.gwt.xml file. Maybe you forgot that?
-- J.
Mathias schrieb am
The most up-to-date tutorial
is https://www.gwtproject.org/gettingstarted-v2.html
It uses maven to setup a best-practice GWT project which should consist of
three modules. One module that contains your GWT code and basically
represents your UI, one module that contains your server side code
Maybe your hibernate is too
new?
https://docs.jboss.org/errai/latest/errai/reference/html_single/#_errai_jpa
indicates that Hibernate 4.1.1 should be used.
-- J.
Mukeya Kassindye schrieb am Donnerstag, 4. April 2024 um 21:29:21 UTC+2:
> Hi,
>
> I can't seem to be able to point out what
2)i wants to test my flask app in same browser but i wants to different
user login and if new user login then previous user don't logout
automatically
If you use Chrome or a Chrome based browser then you could also create two
chrome profiles. Profiles are fully independent of each other
classpath.
> But somehow tomcat is not loading the servlets/services
> Op maandag 25 maart 2024 om 13:14:42 UTC+1 schreef Jens:
>
>> Sure you can also use tomcat or any other servlet container as you just
>> deploy a war file/folder.
>>
>> Does the browser actively rel
:
> Hi Jens,
>
> Thank you for the quick reply. I have tomcat as external web server.
> That should work too, doesn't it?
>
> My files are compiled in {projectfolder}\GWT\war\demo
>
> I am letting tomcat point to that folder and if i would add the following
> lines
CodeServer has a parameter named launcherDir which should point to your
exploded war directory. CodeServer generates a special index.nocache.js
file which needs to be deployed with your war file. Once you have done
that, you just have to open the url to your deployed war file.
So in addition
Nothing that I am aware of. Also I think you need some naming conventions
for your debug ids anyways which makes automatic generation difficult.
Otherwise it will be difficult to write and later understand the UI test if
debug ids are generic like input-0, input-1, input-2. You also need to
Hi,
looking at your build logs it seems you have executed
ant clean dist -Dgwt.tools=/home/aarmugam/GWT_Source_code/gwt-2.4.0/tools/
-Dgwt.version=2.4.0
ant clean dist-dev
-Dgwt.tools=/home/aarmugam/GWT_Source_code/gwt-2.4.0/tools/
-Dgwt.version=2.4.0
In both cases you have set the system
Some mention "some annoying downsides" or "is imperfect in a lot of ways"
regarding gwt-rpc. What are does?
1. Client and server always need to be in sync because of serialization
policy. So a user must reload the web app if you redeploy your application
and have modified shared classes.
If you do not have special needs I think GWT-RPC is still fine especially
with a jakarta version now available. But while it is easy to use it also
has some annoying downsides you have to live with.
However there are quite some options:
- JsInterop based DTOs + JSON.parse/stringify. However you
Generally Java 17 works for running GWT but source level still needs to be
11 for GWT client/shared code as GWT only supports compiling Java 11 source
files. Server code can be anything. If you use GWT-RPC you might need to
add some --add-opens to your server
JVM:
The workaround is to use --add-opens but this basically open the
full java.util package for reflection which is not ideal. I also tried to
replace the custom serializer, but due to the way custom serializers are
loaded (using the exact package name), this doesn't seems possible without
I think I asked the question before: as a long-term GWT-RPC user, what
would be the benefit of moving to some other RPC protocol/mechanism?
Depends on your situation of course. If you want to use your existing
backend with other clients written in other languages then GWT-RPC is a bad
fit.
GWT SDK does not have a Java method to change the Location of the top most
window from within an iframe.
You could use elemental2 library which provides access to most JavaScript
DOM API. Using elemental2 you can do
DomGlobal.window.top.location.replace/assign(url)
But this will only work if
Doctool hasn't been updated yet,
see: https://github.com/gwtproject/gwt/pull/9780
You can install Java 8 for Mac x86
using https://adoptium.net/de/temurin/releases/?version=8
If you use a Mac with Apple Silicon and don't want to install Rosetta 2 you
would need to install Java 8 from a
I am currently stuck with an error in a commercial GWT widget library that
our project uses (GXT v4.0.2). The code generated by that library contains
a bug: it contains a GWT.create(…)-call where the argument is an interface
and not a class.
Actually GWT.create() usually takes an interface and
Seems fine to use the gwtproject.org domain for it. I slightly tend towards
plugins.gwtproject.org/eclipse because it is slightly more descriptive and
then we could also provide plugins.gwtproject.org/browser-extensions to
publish the last working classic dev mode browser extensions for people
ASM is given a class file that has a newer byte code version than ASM
supports. GWT 2.10 depends on ASM 9.2 and supports byte code up to Java 18.
I am pretty sure you have an older ASM version on class path that came
first or some Java 19+ classes.
-- J.
Paul Stockley schrieb am Donnerstag,
I use Jetty but manage it externally and not via GWT or any build tool
plugin. Usually I use a Jetty docker container, preconfigured as much as
possible to match production environment. Then I either mount the generated
*.war file directly into the container or I mount a local webapps folder
For the time being you can install the plugin from
https://github.com/gwt-plugins/gwt-eclipse-plugin/issues/406#issuecomment-1278543693
The linked comment in that issue contains a download to install the plugin
from your disk. Someone also made an update site in some other comments in
that
>
> @Jens I debbuged in DevTools and found that for the server A, there is a
> Post request containing a sessionId sent to it and intercepted by the
> service containing both methods. The same request is sent to the server B
> but doesn't contain a sessionId. I still didn't
Use your browser dev tools to inspect the network request. You should check
if server B sends back a session id cookie and that this session id cookie
is transmitted back to the server for the second method that does
getSession(false). If it doesn't or the session is already invalidated
"Cannot set properties of undefined" is the javascript equivalent of Java
NullPointerException.
So in your code something tried to set the property "BLANK_IMAGE_URL" on
"null".
-- J.
patil.p...@gmail.com schrieb am Montag, 26. September 2022 um 08:48:31
UTC+2:
> Hi
> I having beginners
If you use GWT-RPC or RequestFactory you need to choose a servlet container
that still uses javax.servlet instead of jakarta.servlet because both these
GWT features have a servlet component using javax.servlet.
Other than that, you can choose whatever you want.
-- J.
Valavanur Man schrieb am
You can create the same java file in the same package in your project's
source directory and then adjust the implementation. It should then
override the one in your dependencies.
-- J.
dhia.xd...@gmail.com schrieb am Samstag, 6. August 2022 um 15:49:46 UTC+2:
> do you mean to unzip the jar,
I think first we should put a good Java version policy into place.
Personally I would split this policy into two policies. One for client code
(Compiler) and one for shared/server code.
For client code GWT has two main dependencies: Eclipse JDT and Jetty. So I
would define the minimum required
GWT (gwt-dev) depends on ASM 9.2 which supports up to Java 18. On your
compile classpath you have gwt-websockets which depends on ASM 5.x. Seems
like that ASM version is used during GWT compilation.
ASM's ClassVisitor constructor checks the byte code version of the class
file and if it is too
> The GwtSpring.gwt.xml reads:
> ---
>
>
>
>
>
>
>
>
>
>
>
> ... further details omitted here ...
>
Use slash instead of dots in path="security.core" and
path="security.core.userdetails"
-- J.
--
You received this message
Your interface has a type parameter with no upper bound so it is
effectively Object. Thus GWT does not know which classes to scan because it
will not scan every subclass of Object. Either give your type parameter an
upper bound using a common interface or create a dummy method in your
service
GWT supports the validation API 1.0.0 with hibernate validator as
implementation. GWT itself only ships/depends on the validation api but
implementation needs to be added manually. The documentation how to use it
can be found
at https://www.gwtproject.org/doc/latest/DevGuideValidation.html
> Content in Main.gwt.xml
>
>
>
>
>
>
>
>
>
>
>
>
With that configuration the GWT compiler can see packages
com.cname.proj.client and com.cname.proj.service in your main project.
However your entry point is not in any of these
Yeah as Michael already said, I strongly encourage you to use "-strict" GWT
compiler / DevMode parameter in all of your GWT projects and fix all GWT
compile errors you are then seeing. We should have make that parameter the
default setting long time ago. I really don't see any benefit of not
Without being able to see the project setup this is tough to answer.
However regardless of the exception you are seeing: Classic/Legacy DevMode
will not work with GWT 2.9.0 correctly, because GWT 2.9.0 already uses
JsInterop internally in its Java SDK emulation (e.g. java.util.Date uses
it).
> But only to now getting stuck with:
> ...
> [INFO] --- gwt-maven-plugin:2.10.0:compile (default) @ zhquest-web ---
> [INFO] Compiling module ch.zh.ksta.zhquest.ZHQuestWebDevelopment
> [INFO] [ERROR] Unexpected internal compiler error
> [INFO] java.lang.IllegalArgumentException
> [INFO] at
> So - according to the release notes which mention “FF”, “Chrome”, “IE”
> (for IE11), “Edge”, and “Safari” as new user.agent values I changed that
> to "Chrome, Edge".
>
Not these values are for running HTMLUnit, not for GWT compiler.
Thus my question: what *are* the new valid user.agent
> [INFO] Caused by: java.lang.NoSuchMethodError:
> org.eclipse.jdt.internal.compiler.lookup.MethodBinding.isDefaultMethod()Z
>
This line indicates that you have some version of JDT / ECJ on your
classpath during GWT compilation that is incompatible with the one that GWT
compiler uses. JDT
www.gwtproject.org relatively recently switched to HTTPS only. As seen at
SSLlabs (https://www.ssllabs.com/ssltest/analyze.html?d=gwtproject.org)
only TLS 1.2 and TLS 1.3 are supported by the server. Not sure when the
mentioned error occurs, but you either have to download the plugin using a
UiBinder XML can only call setters on the widget itself. In the
corresponding java file you can call button.getElement().setAttribute().
-- J.
ime...@gmail.com schrieb am Dienstag, 10. Mai 2022 um 20:55:41 UTC+2:
> All,
>
> Is there a way to add a custom attribute to a Button using UiBinder?
> As Google is winding down their direct involvement in the project, the CLA
> bot will be turned off soon, and we'll want to be sure we have an
> explicitly license in all projects that covers contributions, but so far
> this was the only project deficient in this way - and the only project
Haven't all changes been made through gerrit and did require a CLA?
--J.
Colin Alworth schrieb am Donnerstag, 21. April 2022 um 17:34:49 UTC+2:
> See the question raised at
> https://github.com/gwtproject/gwt-site/issues/328.
>
> While gwtproject explicitly licenses all "software and sample
As already said the first thing you should do is to use -strict. This makes
sure GWT compiler does not ignore compile errors. Given you have 12 compile
errors, you want to fix them first.
Next it looks like you have a lot of split points if you have 856
*.cache.js files. Given that 817 of
Chrome / Safari / FireFox are all freeze their user agent string so you can
not know operating system version, device type and browser build number
(not the major version!) anymore. This is done to make fingerprinting more
difficult.
Here is some Chrome documentation:
> I did some tests with one of my larger GWT projects. It takes 3:55 on my
> "old" MacBook Pro 16" i9 2.4 GHz, 64 GB RAM. Same project build on a new
> MacBook Pro M1 Max 64 GB takes roundabout 2:00. That's an incredible
> improvement.
Is that project public? Then I would try it with my M1
Shouldn't really matter if M1 Pro or M1 Max, given that both have the same
CPU. Also the doubled memory bandwidth of the M1 Max shouldn't matter too
much, if at all. Have you run the benchmarks multiple times? I am pretty
sure the 10s difference will become much smaller when using mean numbers
You can use jsinterop-base library. It has a method
'Js.asConstructorFn(Class)'
-- J.
pavel@gmail.com schrieb am Dienstag, 2. November 2021 um 09:49:41 UTC+1:
> Hi all,
>
> I have noticed that the next code returns the undefined value in gwt 2.9.0
>
> public static native Object
There is an annotation called 'DoNotInline' and acts as a compiler hint. So
maybe you can fork GWT and apply that annotation to the method. But then
you could also just change the implementation of the method to fit your
needs.
Obfuscation itself can only be enabled/disabled globally. The only
I think the gecko permutation has very little to no special treatment of IE
11 and there are some bugs reported because of that. So there isn't much to
deprecated for IE 11.
Personally I only use safari, gecko permutation and define safari as
fallback permutation. In addition I use some code
Hi,
really interesting work, but don't you think something like feature
detection should be handled by a dedicated library like Modernizr for
example? You likely want to check for vendor prefixed support when you do
feature detection.
-- J.
peter.j...@gmail.com schrieb am Dienstag, 14.
> [WARN] Server class 'org.ietf.jgss.GSSException' could not be found in the
> web app, but was found on the system classpath
>[ERROR] Found resouce but unrecognized URL format:
> 'jrt:/java.security.jgss/org/ietf/jgss/GSSException.class'
>
JRT urls are available since Java 9 and the
11.07.2021 is a sunday. There are different week numbering systems in the
world which have different first day of week definition. For example in the
EU the first day of the week is monday while in the US / Canada it is
sunday. That is reflected in locales and thus you are seeing that
When you start SuperDevMode it will generate some minimalistic output that
should be stored in the (exploded) war directory produced by your eclipse
plugin. That output basically is a special index.html file for development
(which loads resources from SuperDevMode server instead of your war)
> But how can I replace the Jetty embedded in the GWT Maven plugin? Or is
> there some other way to work-around or fix this?
>
You won't use the GWT Maven plugin to launch any GWT embedded Jetty. You
would use a Maven Jetty plugin directly to deploy your server side code.
Alternatively
Hi,
take a look at com.google.gwt.dom.client.Document class. It has methods for
creating elements and then you can just stitch them together using
Element.appendChild() method.
If you want to abstract the logic a bit and/or you need it as Widget you
could write your own BreadCrumbWidget
> Currently, I'm working on installing WebLogic server 14 my in Eclipse for
> local deployment, however, I'm not sure if this is a better way for our
> local development as I don't have much experience with Weblogic server. The
> production WebLogic server on Linux is maintained by another
>
>
> The code server is ready at http://127.0.0.1:9876/
> Code server started in 4.878 s ms
> *[ERROR] jreLeakPrevention.gcDaemonFail*
> *java.lang.ClassNotFoundException: sun.misc.GC*
>
This can be ignored. GWT's class JettyLauncher tries to fix a class loader
memory leak within sun.misc.GC
For reference:
Jetty ASM issues:
https://github.com/gwtproject/gwt/issues/9606
https://github.com/gwtproject/gwt/issues/9693
https://github.com/gwtproject/gwt/issues/9720
Jakarta servlet support question:
https://github.com/gwtproject/gwt/issues/9727
Other embedded Jetty related issues:
jrt:
Hi,
we all know the issue: DevMode bundles Jetty and people are using it even
though we do not recommend it. Consequently people are complaining that
bundled Jetty is too old. So every once in a while we upgrade it.
Currently with GWT 2.9.0 the situation is:
- GWT SDK is compiled to Java 7
In GWT Boolean, Double and String are represented using their unboxed
primitive types.
See for Double:
https://github.com/gwtproject/gwt/blob/master/user/super/com/google/gwt/emul/java/lang/Double.java#L130
Dropping IE 8-10 shouldn't really hurt. Companies that require it are
probably not upgrading GWT in a fast pace anyways.
However I wouldn't drop IE 11 anytime soon. IE 11 itself is tied to the
lifecycle of Microsoft's operating systems, which means for Windows 10 it
is supported until 2025
> Unreletaed to this, but Thomas one more question if I may: can you see a
> problem with folloging Gradle task:
>
> task gwtCodeServerManual(type: JavaExec) {
> main = 'com.google.gwt.dev.codeserver.CodeServer'
> classpath += files(sourceSets.main.compileClasspath,
>
> I tried using @Deprecated (since="2.0", forRemoval=true) and got
> compilation errors, then i found out that the GWT default JRE emulation
> uses JDK8 java.lang.Deprecated which may or may not have been the culprit
> to my issues.
> So i asked to get confirmation by the community.
>
While
Well ok that devirtual function is clearly broken. Normally these kind of
functions do instanceof dispatches to delegate an abstract method call,
e.g. Number.intValue(), to a concrete implementation, e.g. Integer.intValue.
Below an example how it should look (GWT master branch with an example
>
> And there you have it... absolutely no idea why it's malfunctioning in
> this way. Any help is greatly appreciated!
>
Ok in sourcemaps it looks indeed a bit weird. However there will be
additional JS code executed to convert java.lang.Integer into a primitive
int which is represented by
First of all, when updating GWT SDK you should delete your gwtUnitCache
directory. Historically there has always been some hiccups with the cache
when upgrading GWT. By deleting it you make sure to start a fresh compile
without any cached information.
If that does not help you should take the
> If Maven or some other tool decides to update one of the selected jars
> used by my project, it can introduce a version marked as a high security
> risk. That's something I can't allow.
>
You define a specific library version in your dependency management tool.
There are also tools for
JsInterop is just a convention, so permutations don't make sense here.
Elemental2 is generated from a specification, so it does not use
permutations. If you use Elemental2 you are responsible to apply polyfills
in browsers that do not support the JS features you are using via
elemental2.
Well generally it is a NullPointerException in your onSuccess method in
FileStorageImpl. Somewhere in your code "null/undefined.inspectivity" is
called. If your final JavaScript that produces the above exception contains
literally the code "null.inspectivity" instead of
> If I'm looking at it correctly, it provides just syntactic sugar on top of
> GWT's own EventBus, right?
Thats true,´.
> From what I can see, problem with "ghost" references in event bus which
> would prevent subscribed objects from being garbage collected is still
> there.
>
Right.
> Thanks for your help. I don't understand this sentence " *Also if you do
> not transfer RequirementImpl directly but instead an interface that
> RequirementImpl implements, then GWT Compiler needs to see the class+source
> of RequirementImpl so it can treat RequirementImpl as a possible
RequirementImpl must implement serializable, needs to have a default
constructor (visibility does not matter), no final fields and there must be
at least one serializable type found for each field that can be assigned to
that field (which must meet the same requirements). Also if you do not
>
> So, where I can expect problems to start manifesting?
>
I think if you can make sure that you only put elemental2 based components
into GWT widgets, then it should work without major issues. But if you have
to add a GWT widget into an elemental2 based component, then you have the
Something like (totally untested) might work:
class WidgetAdapter extends Widget {
WidgetAdapter(elemental2.dom.Element element) {
setElement(Js.uncheckedCast(element
));
}
}
But keep in mind that GWT widgets have been rewritten to be J2CL compatible
(they use jsinterop internally
Any news here?
The Leeroy Jenkins spam is really annoying in code reviews.
-- J.
--
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 an email
to
> Fwiw: IE11 will be EOL for mainstream in October this year:
> https://www.swyx.io/writing/ie11-eol/ (of course, for enterprise
> customers this will be longer; my opinion is that those companies that have
> enough money to pay for special Microsoft support contract could also pay a
>
>
>
> I suspect this will not work except in gradle, which picks the highest
> version in the case of a conflict. Maven picks the "nearest to your
> project", so:
>
>- SomeLibrary depends on c.g.g:gwt-user:2.9.0 (or earlier, with or
>without a BOM)
>- MyProject depends on
I know you can force Gradle to swap out dependencies on the fly, e.g.
replace com.google.gwt with org.gwtproject releases. If that would also be
possible with Maven/Ivy/Bazel then it is just a matter of documentation.
If that is not possible, or not desired, then Google could probably publish
So the Eclipse JDT version GWT uses has a generics bug then. Have you tried
open the project/code in Eclipse to see if Eclipse complains as well? If
Eclipse does not complain then it is probably fixed and we can likely just
upgrade JDT again in GWT.
-- J.
--
You received this message because
My understanding is that:
>
>- these projects/classes are builtin in GWT 2.9
>
> Their old, non J2CL compatible versions are buildin in GWT 2.9. No changes
are made here.
> Is it possible to start preparing now with GWT 2.9 before GWT 3? Maybe if
> we drop gwt-user from the
> Is there any way to correctly extend/replace core GWT emulation?
>
You have to contribute it to GWT SDK so there is only a single emulation
for everyone of that Java SDK class. As soon as you replace a GWT SDK
emulation things can break badly.
-- J.
--
You received this message because
Personally I would not say that GWT widgets are deprecated. They are ported
to be compatible with J2CL, they just look a bit dated because nobody has
done a new fancy CSS for them. So it is generally fine to use them, but you
should not expect that any new components will be added to the
> Other ideas?
>
Maybe because you have used a ES6 / ECMAScript2015 class in your custom JS
instead of a traditional function() based JS class. For example web
components also use ES6 classes and it is not straight forward to use them
with JsInterop / GWT.
I would start SDM / Compiler with
I am not 100% sure since I have not used JsInterop for a long time now but
I would imagine the following:
Currently GWT will think that your native JS class "Car" is located at
com.project.client namespace because that is the package it lives in and
you have not provided a namespace to
> But it fails with the following logs:
> direct call: start
> ConsoleLogger.java:33 FAILED to iterate a @JsType in a List
> ConsoleLogger.java:55 Exception:
> com.google.gwt.core.client.JavaScriptException: (TypeError) : Cannot read
> property 'project' of undefined
> ConsoleLogger.java:33
> I have set the compile flag:
> -generateJsInteropExports
>
You only need this when using @JsType(isNative = false) in your code.
Generally you have to wait until external JS has been loaded before you can
access it in your GWT code. Maybe your GWT code runs too early?
-- J.
--
You
Kind of in the same situation and I figured that using an iframe approach
is probably the best idea. So you would need to refactor your app in a way
that you can launch an external application in an iframe for a given menu
item, basically the content area in your app should be an iframe. That
I use IntelliJ Ultimate and use the bundled Jetty integration plugin of
IntelliJ. This is not the Jetty Runner plugin you are using. The bundled
Jetty integration plugin lets you start a local Jetty just fine via a run
configuration and lets you configure *.war or exploded war files to deploy.
> I hope GWT 2.9 is out "soon", because we're planning to switch to Java 11
> in the coming months, and it would be a burden to maintain a separated Java
> version only for the frontend part (been there, done that with Java 8).
>
Java 11 syntax additions are available in GWT snapshot
Looks like Eclipse wants to resolve classpath entries using Gradle (through
Eclipse Buildship Plugin bundled with Eclipse to support project
configuration based on Gradle).
Maybe Gradle is enabled in your project for any reason, even though you are
using Maven?
-- J.
--
You received this
What does the Eclipse error log show? Sounds like an Eclipse / some plugin
issue and the error log should show some stack trace.
-- J.
--
You received this message because you are subscribed to the Google Groups "GWT
Users" group.
To unsubscribe from this group and stop receiving emails from
> I just got my first positive review and I noticed the 'Add Reviewer/ Add
> CC' buttons and I am wondering if I should manually enter the names you
> suggested previously in the thread?
>
Sure, you would use the Add Reviewer button. The person you add will then
receive an email notification
Usually you would use GWT's ScriptInjector together with ClientBundle +
TextResource/ExternalTextResource. That way you can either embed your
external JS into the GWT JS (TextResource) so it downloads as part of your
app download or you let the GWT app asynchronously download the JS when
Cross reference: https://github.com/gwtproject/gwt/issues/9677
--
You received this message because you are subscribed to the Google Groups "GWT
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to google-web-toolkit+unsubscr...@googlegroups.com.
To
> Do you think a patch like that has any chance to be accepted? or this is
> not considered to be an issue?
>
Seems like a valid behavior for JS libraries to check argument count, so I
guess it should be accepted. Goktug or Roberto should probably review it.
-- J.
--
You received this
You can see here how GWT compiler creates
lambdas:
https://github.com/gwtproject/gwt/blob/master/dev/core/super/com/google/gwt/dev/jjs/intrinsic/com/google/gwt/lang/Runtime.java#L162
In case you also want to try to fix the issue ;-)
-- J.
--
You received this message because you are
> Could someone send a patch?
>
I guess the steering group first needs to make the decision to finally drop
java 7. Maybe ping here
again:
https://groups.google.com/forum/#!topic/google-web-toolkit-contributors/tMR3Dv1YBBE
-- J.
--
You received this message because you are subscribed to
Some projects are already moved to GitHub gwtproject organization.
https://github.com/gwtproject
-- J.
--
You received this message because you are subscribed to the Google Groups "GWT
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
> Do you know if there is a resource where all modules and its repository
> are documented? I saw some google doc before, but I do not know if it is
> the last resource with all github repo.
>
Only that google doc and ci.vertispan.com basically.
-- J.
--
You received this message because
1 - 100 of 2941 matches
Mail list logo
