Thank Thomas, I will take a deeper look.
--
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 post to this group, sen
This is true. As I reported allready above all our projects been built
succesfully and working. And debug works great. Except little noise in the
buildlog
--
You received this message because you are subscribed to the Google Groups "GWT
Users" group.
To unsubscribe from this group and stop rec
The change in review is NOT about a broken build, it's only about too much
logging. It's NOT related to your issue, which still needs to be investigated
on your side (why is a javadoc task looking into gwt-user?)
--
You received this message because you are subscribed to the Google Groups "GWT
David,
In this case I reverted back to an older snapshot. It is not a problem that
a GWT developer accidental broke the master build. However, the fix being
stuck in "review" for more than 24hrs is...
On Friday, June 10, 2016 at 8:53:33 AM UTC-7, David Becker wrote:
>
> The code review link Rob
Also, it addresses Filipe's issue, but Hristo's one is different (and if you
ask me, not actually a problem with GWT; not until proven otherwise): why does
a javadoc task look at source files in gwt-user?
--
You received this message because you are subscribed to the Google Groups "GWT
Users"
The code review link Roberto mentioned says it's still under review and
hasn't been merged yet.
-.. .- ...- .. -.....-... . -.-. -.- . .-.
On Fri, Jun 10, 2016 at 8:50 AM, Hristo Stoyanov
wrote:
> Thanks Roberto,
> Just a to confirm that the issue is still with us - i did a new build a
Thanks Roberto,
Just a to confirm that the issue is still with us - i did a new build a few
seconds ago.
On Thursday, June 9, 2016 at 10:55:26 PM UTC-7, Roberto Lublinerman wrote:
>
> The error messages were introduced by mistake in the JSNI error reporting
> fix (https://gwt-review.googlesource
The error messages were introduced by mistake in the JSNI error reporting
fix (https://gwt-review.googlesource.com/#/c/15080) and the fix for those
is up for review https://gwt-review.googlesource.com/#/c/15120/
On Thursday, June 9, 2016 at 8:55:36 AM UTC-7, Hristo Stoyanov wrote:
>
> Thomas, ye
Thomas, yes, it is a javadoc failure, and it is still there. I just
re-tried.
On Thursday, June 9, 2016 at 5:40:24 AM UTC-7, Thomas Broyer wrote:
>
> I see Hristo's error is in a "javadoc" task, could it be the same (or
> similar) for you?
>
> On Thursday, June 9, 2016 at 1:18:02 PM UTC+2, Filip
I`m getting the same error messages with our project
[INFO]Errors in
gen/com/google/gwt/lang/delightex_00046UiTest__EntryMethodHolder.java
[INFO]Errors in com/google/gwt/emul/java/lang/Object.java
. more and more
and finally
[INFO]Compiling 1 permutation
[INFO] Compiling
I see Hristo's error is in a "javadoc" task, could it be the same (or
similar) for you?
On Thursday, June 9, 2016 at 1:18:02 PM UTC+2, Filipe Sousa wrote:
>
> Done that and still have the same errors. Despite the errors the project
> works as if had no errors
>
> $ java -version
> java version "
Hmm... strange. Tried SNAPSHOT from maven and do not see errors too.
On Thursday, June 9, 2016 at 2:33:57 PM UTC+3, Alexabder Leshkin wrote:
>
> I tried local buid (
> https://gwt.googlesource.com/gwt/+/44c3e966e5f8556bda7e749fdbb63dfeeeb39a20)
> and do not see compile errors.
>
> On Thursday, Ju
I tried local buid (
https://gwt.googlesource.com/gwt/+/44c3e966e5f8556bda7e749fdbb63dfeeeb39a20)
and do not see compile errors.
On Thursday, June 9, 2016 at 1:50:47 PM UTC+3, Thomas Broyer wrote:
>
>
> All: anyone tried to build it locally to make sure it's not due to a
> corrupted JAR during u
Done that and still have the same errors. Despite the errors the project
works as if had no errors
$ java -version
java version "1.8.0_92"
Java(TM) SE Runtime Environment (build 1.8.0_92-b14)
Java HotSpot(TM) 64-Bit Server VM (build 25.92-b14, mixed mode)
$ ant -version
Apache Ant(TM) version 1.
+rluble, +goktug
Roberto, Goktug, any idea?
This comes from one of these changes:
http://build.gwtproject.org/job/gwt/520/changes
http://build.gwtproject.org/job/gwt/521/changes
All: anyone tried to build it locally to make sure it's not due to a
corrupted JAR during upload to Sonatype OSSRH?
O
Seeing the same problems (maven build). Worked fine 10 hrs ago though, so
the latest snapshot seems hosed.
Regards,
Henrik
On Thursday, June 9, 2016 at 8:14:47 AM UTC+2, Hristo Stoyanov wrote:
>
> I started getting the following errors with Gradle builds and the latest
> GWT 2.8.-SNAPSHOT - a
Same here
[INFO]Errors in com/google/gwt/emul/java/lang/Object.java
[INFO]Errors in com/google/gwt/core/client/GWT.java
[INFO]Errors in com/google/gwt/core/client/GWT.java
[INFO]Errors in com/google/gwt/core/client/GWT.java
[INFO]Errors in com/google/gwt/core/client/GWT.java
[I
I started getting the following errors with Gradle builds and the latest
GWT 2.8.-SNAPSHOT - any idea ?
===
/root/.gradle/caches/modules-2/files-2.1/com.google.gwt/gwt-user/2.8.0-SNAPSHOT/c7913836bdcf2423552e6355ad17fbd
18 matches
Mail list logo
