Re: Types not resolved when upgrading to GWT 2.7.0 ?
Thanks @Jens, I merged them and it all compiles well. The errors were a bit misleading as apart from the Character errors I got a lot of cannot be resolved to a type at strange places in my code... BTW: it seems to compile fine with compiler source/target set to java 1.8 (no need to set it to 1.7). -- You received this message because you are subscribed to the Google Groups Google Web Toolkit 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, send email to google-web-toolkit@googlegroups.com. Visit this group at http://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
Re: Types not resolved when upgrading to GWT 2.7.0 ?
BTW: it seems to compile fine with compiler source/target set to java 1.8 (no need to set it to 1.7). If you build from trunk you can already use lambda + method references ;-) -- J. -- You received this message because you are subscribed to the Google Groups Google Web Toolkit 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, send email to google-web-toolkit@googlegroups.com. Visit this group at http://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
Re: Types not resolved when upgrading to GWT 2.7.0 ?
Cool, thanks ;) -- You received this message because you are subscribed to the Google Groups Google Web Toolkit 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, send email to google-web-toolkit@googlegroups.com. Visit this group at http://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
Types not resolved when upgrading to GWT 2.7.0 ?
I am trying to upgrade to GWT 2.7.0 (from 2.6.1), and keeping getting these strange errors, below are a few of them. I compile with java 8, but did put the target and source on java 1.7. I tried several thinks, but can't get it resolved Any idea what this could be ? [INFO] [ERROR] Errors in 'jar:file:/1.2-SNAPSHOT/ited-gwt-client-1.2-SNAPSHOT-sources.jar!/com/EffectActionInsertOrAdd.java' [INFO] [ERROR] com.EffectAction cannot be resolved to a type [INFO] [ERROR] Errors in 'jar:file:/Maven/repository/com/google/gwt/gwt-user/2.7.0/gwt-user-2.7.0.jar!/com/google/gwt/emul/java/lang/Long.java' [INFO] [ERROR] Line 181: The method forDigit(int, int) in the type Character is not applicable for the arguments (int) [INFO] [ERROR] Line 184: The method forDigit(int, int) in the type Character is not applicable for the arguments (int) [INFO] [ERROR] Line 191: The method forDigit(int, int) in the type Character is not applicable for the arguments (int) [INFO] [ERROR] Line 188: The method forDigit(int, int) in the type Character is not applicable for the arguments (int) [INFO] [ERROR] Line 228: The method forDigit(int, int) in the type Character is not applicable for the arguments (int) -- You received this message because you are subscribed to the Google Groups Google Web Toolkit 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, send email to google-web-toolkit@googlegroups.com. Visit this group at http://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
Re: Types not resolved when upgrading to GWT 2.7.0 ?
Hmm sounds like a bug or you have two different gwt-user.jar on class path (2.6 and 2.7). Check mvn dependency:tree. Character.forDigit(int) does only exist in the super sourced version of Character and is used by super sourced versions of Character and Long. This change has been introduced by commit https://gwt.googlesource.com/gwt/+/84545ae6961e3b20891f917c0f58015f3f78c1b1 Looks like the compiler does see Character.forDigit(int) in the super sourced version of Character while analyzing the super sourced version of Long provided by GWT 2.7. -- J. -- You received this message because you are subscribed to the Google Groups Google Web Toolkit 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, send email to google-web-toolkit@googlegroups.com. Visit this group at http://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
Re: Types not resolved when upgrading to GWT 2.7.0 ?
@Jens: thanks for the input. No, I only have a 2.7 version, also in the dependency maven tree. But I think my own Character super version and that off GWT don't like each other. I notice that if I remove my version, I do get some other errors, but not the ones in my first post. Mine contains some methods like isSpace(char). Should they be merged? or does one overwrites the other completely? -- You received this message because you are subscribed to the Google Groups Google Web Toolkit 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, send email to google-web-toolkit@googlegroups.com. Visit this group at http://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
Re: Types not resolved when upgrading to GWT 2.7.0 ?
Oh you have your own Character emulation based on the one of GWT 2.6. Well of course you must merge them since you probably don't have your own version of Long and thus the GWT 2.7 version of Long expects that Character has the method forDigit(int,int). But your version currently does not have that method since it is based on GWT 2.6 code that you have copied back in the days. Things would be easier if you would checkout GWT, make a branch with your changes and then rebase that branch on top of master / 2.7 tag / 2.8 tag (in the future). That way the rebasing process would have merged things together (or end up in a conflict state that you must solve). We do that at work as well for a couple of custom patches and it works well. You never really get into an inconsistent state that way. -- J. -- You received this message because you are subscribed to the Google Groups Google Web Toolkit 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, send email to google-web-toolkit@googlegroups.com. Visit this group at http://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
