On Tue, Mar 18, 2014 at 4:10 PM, Stephen Haberman <
stephen.haber...@gmail.com> wrote:
>
> > Neither one (depending on your build tool though).
>
> Sure, I get that Maven/Gradle/Ant will go through a copy-to-target step
> first, and so not use any src/... artifacts. So, for them, having the
> Jett
> Neither one (depending on your build tool though).
Sure, I get that Maven/Gradle/Ant will go through a copy-to-target step
first, and so not use any src/... artifacts. So, for them, having the
Jetty classloader not use the project classpath makes sense.
But at least we way run DevMode in Eclip
>
> Maybe it's a GPE issue after all (I never tried IntelliJ IDEA for webapps;
> I tend to prefer embedded servers these days, rather than wars deployed
> into servlet containers).
>
You have the same issue in IntelliJ. IntelliJ can create an example GWT
project that will have src + war folder
On Monday, March 17, 2014 4:50:47 PM UTC+1, Stephen Haberman wrote:
>
> Hi Thomas,
>
> > (or rather, it'll work "too well", and won't detect that "something is
> > missing in WEB-INF/lib".
>
> I'm attempting to follow along, but classloader semantics are "fun", so
> apologies if I'm wrong som
Hi Thomas,
> (or rather, it'll work "too well", and won't detect that "something is
> missing in WEB-INF/lib".
I'm attempting to follow along, but classloader semantics are "fun", so
apologies if I'm wrong somewhere...
So, to clarify, if I have a dependency, say foo.jar, that isn't GWT, and
isn'
On Mon, Mar 17, 2014 at 1:54 AM, Jens wrote:
> +1 The problem is determining what "provided by the server" actually means
>> though. Servers generally just use their classpath, but in our case the
>> classpath generally (because of Eclipse, and because of how DevMode loads
>> client code too) con
>
> +1 The problem is determining what "provided by the server" actually means
> though. Servers generally just use their classpath, but in our case the
> classpath generally (because of Eclipse, and because of how DevMode loads
> client code too) contains the classes that also are in WEB-INF/l
On Sunday, March 9, 2014 3:02:31 PM UTC+1, Jens wrote:
>
> In the end, I wonder if we shouldn't just basically revert
>> https://code.google.com/p/google-web-toolkit/source/detail?r=4944,
>> except issuing a warning when we find the class in the system classpath
>> (but without automatically a
On Friday, March 14, 2014 6:03:15 AM UTC+1, gslender wrote:
>
> Thanks Thomas. Can you also explain how things operate for GAE when and if
> I were to employ SuperDev mode
>
Heavily depends whether you're using GWT-RPC or not.
> - I thought there would be no impact as the GWT module is loade
Thanks Thomas. Can you also explain how things operate for GAE when and if
I were to employ SuperDev mode - I thought there would be no impact as the
GWT module is loaded by redirecting the HTML script to the compiler web
server, but when I looked at this before I ran into some issues where the
It does not apply to GAE as they just hook into DevMode extension points
replacing the JettyLauncher with their
own:
https://code.google.com/p/googleappengine/source/browse/trunk/java/src/main/com/google/appengine/tools/development/gwt/AppEngineLauncher.java
On Thursday, March 13, 2014 3:18:43
Does any of the changes in 2.6 in relation to the Jetty server and class
loaders mentioned here impact users who are building GWT apps with the GAE
dev server? I've yet to fully explore 2.6 with the current GAE releases,
and haven't really followed the issue you've outlined here either, but
wan
As I was writing a memo about the issue, it happened to me that there could
be an easy workaround: special-case org.eclipse.jetty. classes to allow
loading them from the system classloader as a fallback, without adding the
containing classpath entry (most likely gwt-dev.jar) to the webapp
class
To be honest I don't even understand full extend of the problem, I mostly
followed what is already there. We don't use most of this stuff internally.
I trust you making the best choice for external users and I'm fine with it
as long as it doesn't break internal users.
On Sat, Mar 8, 2014 at 5:12
>
> In the end, I wonder if we shouldn't just basically revert
> https://code.google.com/p/google-web-toolkit/source/detail?r=4944, except
> issuing a warning when we find the class in the system classpath (but
> without automatically adding the JAR to the classpath and instead just
> saying t
On Sunday, March 9, 2014 1:09:23 AM UTC+1, Thomas Broyer wrote:
>
> Hi all,
>
> The update from Jetty 6 to Jetty 8 wasn't without regressions. One of them
> is a classloader issue.
>
> First, when starting DevMode, sometimes (IIRC, not for all projects, might
> be because I tried with a WEB-INF
16 matches
Mail list logo
