[gwt-contrib] Re: Can't build trunk with Java 6?
Yep, I have just checked and sourcemap-rebased.jar is version 51.0 (i.e. compiled with Java7). GWT takes this dependency from the public closure release. On Thu, Jan 9, 2014 at 3:13 PM, Jens jens.nehlme...@gmail.com wrote: Looks like IE6 hasn't been completely removed? Oh that reminds me of my comment I have done in https://gwt-review.googlesource.com/#/c/5055/ after it was already merged. The warning is caused by the IE 9 permutation but as the compiled code works I had forget about it. -- J. -- 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 an email to google-web-toolkit-contributors+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[gwt-contrib] Re: Can't build trunk with Java 6?
Looks like IE6 hasn't been completely removed? Oh that reminds me of my comment I have done in https://gwt-review.googlesource.com/#/c/5055/ after it was already merged. The warning is caused by the IE 9 permutation but as the compiled code works I had forget about it. -- J. -- 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 an email to google-web-toolkit-contributors+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[gwt-contrib] Re: Can't build trunk
Ok, that makes sense, and sounds like my fault. I'll have a look at it later today.Thanks for catching this. On Tue, Oct 6, 2009 at 1:31 PM, bond raul.pel...@mail.ee wrote: I have same problem with Mail sample. Could it be because of my locale - decimal symbol is comma? Generated BinderImpl also shows it: f_DockLayoutPanel1.addNorth(topPanel, 5,00); f_SplitLayoutPanel2.addWest(shortcuts, 192,00); f_SplitLayoutPanel2.addNorth(mailList, 200,00); On 6 Oct, 18:32, Freeland Abbott fabb...@google.com wrote: On Tue, Oct 6, 2009 at 2:35 AM, tfga thiago...@gmail.com wrote: Thank you for you very detailed message, Freeland. Regarding [4] (LONG compiler errors in Browser): I only get those when I run ant from Eclipse. When I run it from the It would make (some) sense for Eclipse to put its own jars onto your classpath, so I think that's your version skew problem there, yes. command line, I get a different set of errors (see message 3). What about these? Well, at root I'm going to give you a similar answer: we don't get those errors, so it seems something is screwy in your setup; try going over your classpath with a fine-toothed comb. (For what it's worth, I just tried again on XP at revision 6301, no issues for me.) If your only errors are in the samples, the dist-dev target may help you (by skipping the problem). That's not a feel-good solution, though, since it should work and does here. It looks like Joel's r6192 (Sep 22) changed the add...(...) signatures and supported uiBinder for Mail sample. As Eric alludes, the Mail_BinderImpl class is generated, and if I'm reading the sense of the error right, you're getting new calls from that generated code against an old definition for the DockPanelLayout class... so where's that old class coming from? (I don't think the default build files save generated output at all persistently, so Eric's suggestion to hunt down the *_BinderImpl files will, I think, not help much---I don't think they're persistent, and even if they are, I *think* the message says they're more right, i.e. post-6192, and it's the DockPanelLayout class that's stale.) If you were still building using Eclipse, I'd ask whether you were using the Google Plugin for Eclipse and if so whether it was using a (different) GWT runtime when building your GWT project itself; that'd get you two sets of classes (one from the source, modern; one from the runtime, probably a stale release)... instead, I'm going to ask whether you have a CLASSPATH environment variable set, and perhaps including old/released GWT jars. But the end result is still going to be look at your ant -v classpath very, very carefully, no longer for conflicting Eclipse stuff in this case but for conflicting GWT stuff. And you might want to make sure you don't have local mods on DockPanelLayout, though that should be an idiot check since you've said it's a clean checkout. Still, I've been a dumber idiot than that on occasion I was using the ant that came with Eclipse; I tried using the official, stand-alone one from apache and got the same result. On Oct 5, 12:29 am, Freeland Abbott fabb...@google.com wrote: Going back to some of your original questions: 1. The default behavior is to build cross-platform. If you only care about the platform you're on, there's a *-one family of targets, and to leave things like samples and tools behind, a *-dev family. Try ant dist-dev to make a one-platform distribution without samples or tools, although you might find you actually *want* especially the tools. But most of us don't iterate on them as often, which is why they're left out from those rules. Or, use dist-one if you do want them. 2. As a hack to your svn issue, if you just pre-define the ant properties it's supposed to set from svn info and svnversion, the SvnInfoTask will skip over the work (and thus skip not finding svn). That'd look something like: - ant -dgwt.svnrev=tr...@5678 dist-one 3. There's no reason cygwin shouldn't work for you, but you don't need it either. There's a perfectly good native Windows svn at http://www.collab.net/downloads/subversion/. If you're already using cygwin, e.g. for git, of course, then as noted it *should* have worked fine... we need[*] a svnversion and svn executable on the command line, but we don't care which port or environment. 4. Your LONG compiler errors in Browser are screwy; as Eric says, we don't see them... and we're desparately trying to retire our swt dependency anyway. But at a guess, I suspect you've got different Eclipse jars on your classpath than you should, especially if you're building from some Eclipse. I haven't done an
[gwt-contrib] Re: Can't build trunk
Just added an issue: http://code.google.com/p/google-web-toolkit/issues/detail?id=4111 On Wed, Oct 7, 2009 at 9:30 AM, Joel Webber j...@google.com wrote: Ok, that makes sense, and sounds like my fault. I'll have a look at it later today.Thanks for catching this. On Tue, Oct 6, 2009 at 1:31 PM, bond raul.pel...@mail.ee wrote: I have same problem with Mail sample. Could it be because of my locale - decimal symbol is comma? Generated BinderImpl also shows it: f_DockLayoutPanel1.addNorth(topPanel, 5,00); f_SplitLayoutPanel2.addWest(shortcuts, 192,00); f_SplitLayoutPanel2.addNorth(mailList, 200,00); On 6 Oct, 18:32, Freeland Abbott fabb...@google.com wrote: On Tue, Oct 6, 2009 at 2:35 AM, tfga thiago...@gmail.com wrote: Thank you for you very detailed message, Freeland. Regarding [4] (LONG compiler errors in Browser): I only get those when I run ant from Eclipse. When I run it from the It would make (some) sense for Eclipse to put its own jars onto your classpath, so I think that's your version skew problem there, yes. command line, I get a different set of errors (see message 3). What about these? Well, at root I'm going to give you a similar answer: we don't get those errors, so it seems something is screwy in your setup; try going over your classpath with a fine-toothed comb. (For what it's worth, I just tried again on XP at revision 6301, no issues for me.) If your only errors are in the samples, the dist-dev target may help you (by skipping the problem). That's not a feel-good solution, though, since it should work and does here. It looks like Joel's r6192 (Sep 22) changed the add...(...) signatures and supported uiBinder for Mail sample. As Eric alludes, the Mail_BinderImpl class is generated, and if I'm reading the sense of the error right, you're getting new calls from that generated code against an old definition for the DockPanelLayout class... so where's that old class coming from? (I don't think the default build files save generated output at all persistently, so Eric's suggestion to hunt down the *_BinderImpl files will, I think, not help much---I don't think they're persistent, and even if they are, I *think* the message says they're more right, i.e. post-6192, and it's the DockPanelLayout class that's stale.) If you were still building using Eclipse, I'd ask whether you were using the Google Plugin for Eclipse and if so whether it was using a (different) GWT runtime when building your GWT project itself; that'd get you two sets of classes (one from the source, modern; one from the runtime, probably a stale release)... instead, I'm going to ask whether you have a CLASSPATH environment variable set, and perhaps including old/released GWT jars. But the end result is still going to be look at your ant -v classpath very, very carefully, no longer for conflicting Eclipse stuff in this case but for conflicting GWT stuff. And you might want to make sure you don't have local mods on DockPanelLayout, though that should be an idiot check since you've said it's a clean checkout. Still, I've been a dumber idiot than that on occasion I was using the ant that came with Eclipse; I tried using the official, stand-alone one from apache and got the same result. On Oct 5, 12:29 am, Freeland Abbott fabb...@google.com wrote: Going back to some of your original questions: 1. The default behavior is to build cross-platform. If you only care about the platform you're on, there's a *-one family of targets, and to leave things like samples and tools behind, a *-dev family. Try ant dist-dev to make a one-platform distribution without samples or tools, although you might find you actually *want* especially the tools. But most of us don't iterate on them as often, which is why they're left out from those rules. Or, use dist-one if you do want them. 2. As a hack to your svn issue, if you just pre-define the ant properties it's supposed to set from svn info and svnversion, the SvnInfoTask will skip over the work (and thus skip not finding svn). That'd look something like: - ant -dgwt.svnrev=tr...@5678 dist-one 3. There's no reason cygwin shouldn't work for you, but you don't need it either. There's a perfectly good native Windows svn at http://www.collab.net/downloads/subversion/. If you're already using cygwin, e.g. for git, of course, then as noted it *should* have worked fine... we need[*] a svnversion and svn executable on the command line, but we don't care which port or environment. 4. Your LONG compiler errors in Browser are screwy; as Eric says, we don't see them... and we're desparately trying to retire our swt dependency anyway. But at a guess, I
[gwt-contrib] Re: Can't build trunk
In msg 3 above, It looks like your generated files are going in: c:\DOCUME~1\tfga\CONFIG~1\Temp The 'addNorth(Widget, int)' is the correct signature. That other signature (Shortcuts, int, int) being reported from the BinderImpl file is stale. The directory .../Temp isn't going to get cleared out by 'ant clean' so maybe you need to remove files from there manually (maybe a red herring, this could just be a diagnostic from UiBinder). Could be there is a permissions problem and the old generated files aren't getting overwritten? Maybe a stale version somewhere else on your classpath? Search around for files with the name *Mail_BinderImpl*.java. Those are transient and can be deleted. On Tue, Oct 6, 2009 at 2:35 AM, tfga thiago...@gmail.com wrote: Thank you for you very detailed message, Freeland. Regarding [4] (LONG compiler errors in Browser): I only get those when I run ant from Eclipse. When I run it from the command line, I get a different set of errors (see message 3). What about these? I was using the ant that came with Eclipse; I tried using the official, stand-alone one from apache and got the same result. On Oct 5, 12:29 am, Freeland Abbott fabb...@google.com wrote: Going back to some of your original questions: 1. The default behavior is to build cross-platform. If you only care about the platform you're on, there's a *-one family of targets, and to leave things like samples and tools behind, a *-dev family. Try ant dist-dev to make a one-platform distribution without samples or tools, although you might find you actually *want* especially the tools. But most of us don't iterate on them as often, which is why they're left out from those rules. Or, use dist-one if you do want them. 2. As a hack to your svn issue, if you just pre-define the ant properties it's supposed to set from svn info and svnversion, the SvnInfoTask will skip over the work (and thus skip not finding svn). That'd look something like: - ant -dgwt.svnrev=tr...@5678 dist-one 3. There's no reason cygwin shouldn't work for you, but you don't need it either. There's a perfectly good native Windows svn at http://www.collab.net/downloads/subversion/. If you're already using cygwin, e.g. for git, of course, then as noted it *should* have worked fine... we need[*] a svnversion and svn executable on the command line, but we don't care which port or environment. 4. Your LONG compiler errors in Browser are screwy; as Eric says, we don't see them... and we're desparately trying to retire our swt dependency anyway. But at a guess, I suspect you've got different Eclipse jars on your classpath than you should, especially if you're building from some Eclipse. I haven't done an exhaustive check in all the jars, but in $GWT_TOOLS/lib/eclipse/org.eclipse.swt.gtk-linux-3.2.1.jar I see only the ...internal.gtk.LONG class, *not* the internal.LONG variant. I suspect you're getting a more modern Eclipse jar, and that they must have refactored it up or somesuch. Ant -v will report the classpath; I suspect you'll find a stray jar from outside the GWT and GWT_TOOLS hierarchies which is messing you up. (My own ant -v is below, but you shouldn't need to do the 1:1 matching; just look for something from the wrong directories!) - [gwt.javac] 'C:\Documents and Settings\fabbott\My Documents\GWTs\collections\build\out\dev\linux\bin;C:\Documents and Settings\fabbott\My Documents\GWTs\tools\lib\eclipse\org.eclipse.swt.gtk-linux-3.2.1.jar;C:\Documents and Settings\fabbott\My Documents\GWTs\collections\build\out\dev\core\bin;C:\Documents and Settings\fabbott\My Documents\GWTs\collections\build\out\dev\core\alldeps.jar;C:\Program Files\apache-ant-1.7.1\lib\ant-launcher.jar;C:\Program Files\apache-ant-1.7.1\lib\ant-antlr.jar;C:\Program Files\apache-ant-1.7.1\lib\ant-apache-bcel.jar;C:\Program Files\apache-ant-1.7.1\lib\ant-apache-bsf.jar;C:\Program Files\apache-ant-1.7.1\lib\ant-apache-log4j.jar;C:\Program Files\apache-ant-1.7.1\lib\ant-apache-oro.jar;C:\Program Files\apache-ant-1.7.1\lib\ant-apache-regexp.jar;C:\Program Files\apache-ant-1.7.1\lib\ant-apache-resolver.jar;C:\Program Files\apache-ant-1.7.1\lib\ant-commons-logging.jar;C:\Program Files\apache-ant-1.7.1\lib\ant-commons-net.jar;C:\Program Files\apache-ant-1.7.1\lib\ant-contrib-1.0b3.jar;C:\Program Files\apache-ant-1.7.1\lib\ant-jai.jar;C:\Program Files\apache-ant-1.7.1\lib\ant-javamail.jar;C:\Program Files\apache-ant-1.7.1\lib\ant-jdepend.jar;C:\Program Files\apache-ant-1.7.1\lib\ant-jmf.jar;C:\Program Files\apache-ant-1.7.1\lib\ant-jsch.jar;C:\Program Files\apache-ant-1.7.1\lib\ant-junit.jar;C:\Program
[gwt-contrib] Re: Can't build trunk
On Tue, Oct 6, 2009 at 2:35 AM, tfga thiago...@gmail.com wrote: Thank you for you very detailed message, Freeland. Regarding [4] (LONG compiler errors in Browser): I only get those when I run ant from Eclipse. When I run it from the It would make (some) sense for Eclipse to put its own jars onto your classpath, so I think that's your version skew problem there, yes. command line, I get a different set of errors (see message 3). What about these? Well, at root I'm going to give you a similar answer: we don't get those errors, so it seems something is screwy in your setup; try going over your classpath with a fine-toothed comb. (For what it's worth, I just tried again on XP at revision 6301, no issues for me.) If your only errors are in the samples, the dist-dev target may help you (by skipping the problem). That's not a feel-good solution, though, since it should work and does here. It looks like Joel's r6192 (Sep 22) changed the add...(...) signatures and supported uiBinder for Mail sample. As Eric alludes, the Mail_BinderImpl class is generated, and if I'm reading the sense of the error right, you're getting new calls from that generated code against an old definition for the DockPanelLayout class... so where's that old class coming from? (I don't think the default build files save generated output at all persistently, so Eric's suggestion to hunt down the *_BinderImpl files will, I think, not help much---I don't think they're persistent, and even if they are, I *think* the message says they're more right, i.e. post-6192, and it's the DockPanelLayout class that's stale.) If you were still building using Eclipse, I'd ask whether you were using the Google Plugin for Eclipse and if so whether it was using a (different) GWT runtime when building your GWT project itself; that'd get you two sets of classes (one from the source, modern; one from the runtime, probably a stale release)... instead, I'm going to ask whether you have a CLASSPATH environment variable set, and perhaps including old/released GWT jars. But the end result is still going to be look at your ant -v classpath very, very carefully, no longer for conflicting Eclipse stuff in this case but for conflicting GWT stuff. And you might want to make sure you don't have local mods on DockPanelLayout, though that should be an idiot check since you've said it's a clean checkout. Still, I've been a dumber idiot than that on occasion I was using the ant that came with Eclipse; I tried using the official, stand-alone one from apache and got the same result. On Oct 5, 12:29 am, Freeland Abbott fabb...@google.com wrote: Going back to some of your original questions: 1. The default behavior is to build cross-platform. If you only care about the platform you're on, there's a *-one family of targets, and to leave things like samples and tools behind, a *-dev family. Try ant dist-dev to make a one-platform distribution without samples or tools, although you might find you actually *want* especially the tools. But most of us don't iterate on them as often, which is why they're left out from those rules. Or, use dist-one if you do want them. 2. As a hack to your svn issue, if you just pre-define the ant properties it's supposed to set from svn info and svnversion, the SvnInfoTask will skip over the work (and thus skip not finding svn). That'd look something like: - ant -dgwt.svnrev=tr...@5678 dist-one 3. There's no reason cygwin shouldn't work for you, but you don't need it either. There's a perfectly good native Windows svn at http://www.collab.net/downloads/subversion/. If you're already using cygwin, e.g. for git, of course, then as noted it *should* have worked fine... we need[*] a svnversion and svn executable on the command line, but we don't care which port or environment. 4. Your LONG compiler errors in Browser are screwy; as Eric says, we don't see them... and we're desparately trying to retire our swt dependency anyway. But at a guess, I suspect you've got different Eclipse jars on your classpath than you should, especially if you're building from some Eclipse. I haven't done an exhaustive check in all the jars, but in $GWT_TOOLS/lib/eclipse/org.eclipse.swt.gtk-linux-3.2.1.jar I see only the ...internal.gtk.LONG class, *not* the internal.LONG variant. I suspect you're getting a more modern Eclipse jar, and that they must have refactored it up or somesuch. Ant -v will report the classpath; I suspect you'll find a stray jar from outside the GWT and GWT_TOOLS hierarchies which is messing you up. (My own ant -v is below, but you shouldn't need to do the 1:1 matching; just look for something from the wrong directories!) - [gwt.javac] 'C:\Documents and Settings\fabbott\My Documents\GWTs\collections\build\out\dev\linux\bin;C:\Documents
[gwt-contrib] Re: Can't build trunk
I have same problem with Mail sample. Could it be because of my locale - decimal symbol is comma? Generated BinderImpl also shows it: f_DockLayoutPanel1.addNorth(topPanel, 5,00); f_SplitLayoutPanel2.addWest(shortcuts, 192,00); f_SplitLayoutPanel2.addNorth(mailList, 200,00); On 6 Oct, 18:32, Freeland Abbott fabb...@google.com wrote: On Tue, Oct 6, 2009 at 2:35 AM, tfga thiago...@gmail.com wrote: Thank you for you very detailed message, Freeland. Regarding [4] (LONG compiler errors in Browser): I only get those when I run ant from Eclipse. When I run it from the It would make (some) sense for Eclipse to put its own jars onto your classpath, so I think that's your version skew problem there, yes. command line, I get a different set of errors (see message 3). What about these? Well, at root I'm going to give you a similar answer: we don't get those errors, so it seems something is screwy in your setup; try going over your classpath with a fine-toothed comb. (For what it's worth, I just tried again on XP at revision 6301, no issues for me.) If your only errors are in the samples, the dist-dev target may help you (by skipping the problem). That's not a feel-good solution, though, since it should work and does here. It looks like Joel's r6192 (Sep 22) changed the add...(...) signatures and supported uiBinder for Mail sample. As Eric alludes, the Mail_BinderImpl class is generated, and if I'm reading the sense of the error right, you're getting new calls from that generated code against an old definition for the DockPanelLayout class... so where's that old class coming from? (I don't think the default build files save generated output at all persistently, so Eric's suggestion to hunt down the *_BinderImpl files will, I think, not help much---I don't think they're persistent, and even if they are, I *think* the message says they're more right, i.e. post-6192, and it's the DockPanelLayout class that's stale.) If you were still building using Eclipse, I'd ask whether you were using the Google Plugin for Eclipse and if so whether it was using a (different) GWT runtime when building your GWT project itself; that'd get you two sets of classes (one from the source, modern; one from the runtime, probably a stale release)... instead, I'm going to ask whether you have a CLASSPATH environment variable set, and perhaps including old/released GWT jars. But the end result is still going to be look at your ant -v classpath very, very carefully, no longer for conflicting Eclipse stuff in this case but for conflicting GWT stuff. And you might want to make sure you don't have local mods on DockPanelLayout, though that should be an idiot check since you've said it's a clean checkout. Still, I've been a dumber idiot than that on occasion I was using the ant that came with Eclipse; I tried using the official, stand-alone one from apache and got the same result. On Oct 5, 12:29 am, Freeland Abbott fabb...@google.com wrote: Going back to some of your original questions: 1. The default behavior is to build cross-platform. If you only care about the platform you're on, there's a *-one family of targets, and to leave things like samples and tools behind, a *-dev family. Try ant dist-dev to make a one-platform distribution without samples or tools, although you might find you actually *want* especially the tools. But most of us don't iterate on them as often, which is why they're left out from those rules. Or, use dist-one if you do want them. 2. As a hack to your svn issue, if you just pre-define the ant properties it's supposed to set from svn info and svnversion, the SvnInfoTask will skip over the work (and thus skip not finding svn). That'd look something like: - ant -dgwt.svnrev=tr...@5678 dist-one 3. There's no reason cygwin shouldn't work for you, but you don't need it either. There's a perfectly good native Windows svn at http://www.collab.net/downloads/subversion/. If you're already using cygwin, e.g. for git, of course, then as noted it *should* have worked fine... we need[*] a svnversion and svn executable on the command line, but we don't care which port or environment. 4. Your LONG compiler errors in Browser are screwy; as Eric says, we don't see them... and we're desparately trying to retire our swt dependency anyway. But at a guess, I suspect you've got different Eclipse jars on your classpath than you should, especially if you're building from some Eclipse. I haven't done an exhaustive check in all the jars, but in $GWT_TOOLS/lib/eclipse/org.eclipse.swt.gtk-linux-3.2.1.jar I see only the ...internal.gtk.LONG class, *not* the internal.LONG variant. I suspect you're getting a more modern Eclipse jar, and that they must have refactored it
[gwt-contrib] Re: Can't build trunk
Um. cough Yeah, that looks possible... Ray, that's on you if so, yes? Sorry for the goosechase, tfga On Tue, Oct 6, 2009 at 1:31 PM, bond raul.pel...@mail.ee wrote: I have same problem with Mail sample. Could it be because of my locale - decimal symbol is comma? Generated BinderImpl also shows it: f_DockLayoutPanel1.addNorth(topPanel, 5,00); f_SplitLayoutPanel2.addWest(shortcuts, 192,00); f_SplitLayoutPanel2.addNorth(mailList, 200,00); On 6 Oct, 18:32, Freeland Abbott fabb...@google.com wrote: On Tue, Oct 6, 2009 at 2:35 AM, tfga thiago...@gmail.com wrote: Thank you for you very detailed message, Freeland. Regarding [4] (LONG compiler errors in Browser): I only get those when I run ant from Eclipse. When I run it from the It would make (some) sense for Eclipse to put its own jars onto your classpath, so I think that's your version skew problem there, yes. command line, I get a different set of errors (see message 3). What about these? Well, at root I'm going to give you a similar answer: we don't get those errors, so it seems something is screwy in your setup; try going over your classpath with a fine-toothed comb. (For what it's worth, I just tried again on XP at revision 6301, no issues for me.) If your only errors are in the samples, the dist-dev target may help you (by skipping the problem). That's not a feel-good solution, though, since it should work and does here. It looks like Joel's r6192 (Sep 22) changed the add...(...) signatures and supported uiBinder for Mail sample. As Eric alludes, the Mail_BinderImpl class is generated, and if I'm reading the sense of the error right, you're getting new calls from that generated code against an old definition for the DockPanelLayout class... so where's that old class coming from? (I don't think the default build files save generated output at all persistently, so Eric's suggestion to hunt down the *_BinderImpl files will, I think, not help much---I don't think they're persistent, and even if they are, I *think* the message says they're more right, i.e. post-6192, and it's the DockPanelLayout class that's stale.) If you were still building using Eclipse, I'd ask whether you were using the Google Plugin for Eclipse and if so whether it was using a (different) GWT runtime when building your GWT project itself; that'd get you two sets of classes (one from the source, modern; one from the runtime, probably a stale release)... instead, I'm going to ask whether you have a CLASSPATH environment variable set, and perhaps including old/released GWT jars. But the end result is still going to be look at your ant -v classpath very, very carefully, no longer for conflicting Eclipse stuff in this case but for conflicting GWT stuff. And you might want to make sure you don't have local mods on DockPanelLayout, though that should be an idiot check since you've said it's a clean checkout. Still, I've been a dumber idiot than that on occasion I was using the ant that came with Eclipse; I tried using the official, stand-alone one from apache and got the same result. On Oct 5, 12:29 am, Freeland Abbott fabb...@google.com wrote: Going back to some of your original questions: 1. The default behavior is to build cross-platform. If you only care about the platform you're on, there's a *-one family of targets, and to leave things like samples and tools behind, a *-dev family. Try ant dist-dev to make a one-platform distribution without samples or tools, although you might find you actually *want* especially the tools. But most of us don't iterate on them as often, which is why they're left out from those rules. Or, use dist-one if you do want them. 2. As a hack to your svn issue, if you just pre-define the ant properties it's supposed to set from svn info and svnversion, the SvnInfoTask will skip over the work (and thus skip not finding svn). That'd look something like: - ant -dgwt.svnrev=tr...@5678 dist-one 3. There's no reason cygwin shouldn't work for you, but you don't need it either. There's a perfectly good native Windows svn at http://www.collab.net/downloads/subversion/. If you're already using cygwin, e.g. for git, of course, then as noted it *should* have worked fine... we need[*] a svnversion and svn executable on the command line, but we don't care which port or environment. 4. Your LONG compiler errors in Browser are screwy; as Eric says, we don't see them... and we're desparately trying to retire our swt dependency anyway. But at a guess, I suspect you've got different Eclipse jars on your classpath than you should, especially if you're building from some Eclipse. I haven't done an
[gwt-contrib] Re: Can't build trunk
On Oct 6, 2:31 pm, bond raul.pel...@mail.ee wrote: Could it be because of my locale - decimal symbol is comma? Same thing in my locale. On Oct 6, 6:11 pm, Freeland Abbott fabb...@google.com wrote: Um. cough Yeah, that looks possible... Ray, that's on you if so, yes? Sorry for the goosechase, tfga No problem. --~--~-~--~~~---~--~~ http://groups.google.com/group/Google-Web-Toolkit-Contributors -~--~~~~--~~--~--~---
[gwt-contrib] Re: Can't build trunk
You need to run your build under the windows command shell. That probably
means you need to get the native windows svn executable too.
On Sun, Oct 4, 2009 at 1:23 AM, tfga thiago...@gmail.com wrote:
Hi,
I'm trying to build trunk on Windows. I followed the instructions from
http://code.google.com/webtoolkit/makinggwtbetter.html#compiling
The 1st error I got was:
gwt\common.ant.xml:276: Unable to launch command: svn info
So I installed the Cygwin port of svn and added it's path to $PATH.
Now I get this:
linux:
compile:
[mkdir] Created dir: C:\Documents and Settings\tfga\workspace\gwt
\build\out\dev\linux\bin
[gwt.javac] Compiling 11 source files to C:\Documents and Settings\tfga
\workspace\gwt\build\out\dev\linux\bin
[gwt.javac] C:\Documents and Settings\tfga\workspace\gwt\dev\linux\src
\org\eclipse\swt\browser\Browser.java:620: reference to LONG is
ambiguous, both class org.eclipse.swt.internal.gtk.LONG in
org.eclipse.swt.internal.gtk and class org.eclipse.swt.internal.LONG
in org.eclipse.swt.internal match
[gwt.javac] getDisplay().setData(ADD_WIDGET_KEY, new
Object[] {new
LONG(mozillaHandle), this});
[gwt.javac]
^
[gwt.javac] C:\Documents and Settings\tfga\workspace\gwt\dev\linux\src
\org\eclipse\swt\browser\Browser.java:1340: reference to LONG is
ambiguous, both class org.eclipse.swt.internal.gtk.LONG in
org.eclipse.swt.internal.gtk and class org.eclipse.swt.internal.LONG
in org.eclipse.swt.internal match
[gwt.javac] display.setData(ADD_WIDGET_KEY, new Object[] {new LONG
(mozillaHandle), null});
[gwt.javac] ^
[gwt.javac] 2 errors
Why is it running the linux target if I'm using Windows? Do I have
to install the windows native port of svn? And what about these
compilation errors?
Regards,
Thiago
--
Eric Z. Ayers
Google Web Toolkit, Atlanta, GA USA
--~--~-~--~~~---~--~~
http://groups.google.com/group/Google-Web-Toolkit-Contributors
-~--~~~~--~~--~--~---
[gwt-contrib] Re: Can't build trunk
Thank you for you reply, Eric. I was launching ant from within Eclipse. I ran it under cygwin and got a different error (below). I'll try to run it under cmd.exe, as you suggested. gwtc: [java] Compiling module com.google.gwt.sample.mail.Mail [java]Scanning for additional dependencies: file:/C:/Documents %20and%20Settings/tfga/workspace/gwt/samples/mail/src/com/google/gwt/ sample/mail/client/Mail.java [java] Adding '2' new generated units [java] Validating newly compiled units [java] Removing units with errors [java][ERROR] Errors in 'transient source for com.google.gwt.sample.mail.client.Mail_BinderImpl' [java] [ERROR] Line 20: The method addNorth (Widget, double) in the type DockLayoutPanel is not applicable for the arguments (TopPanel, int, int) [java] [ERROR] Line 21: The method addWest (Widget, double) in the type DockLayoutPanel is not applicable for the arguments (Shortcuts, int, int) [java] [ERROR] Line 22: The method addNorth (Widget, double) in the type DockLayoutPanel is not applicable for the arguments (MailList, int, int) [java] See snapshot: c:\DOCUME~1\tfga \CONFIG~1\Temp \com.google.gwt.sample.mail.client.Mail_BinderImpl2569137898788811986.java [java] [ERROR] Unable to find recently-generated type 'com.google.gwt.sample.mail.client.Mail_BinderImpl [java][ERROR] Errors in 'file:/C:/Documents%20and%20Settings/ tfga/workspace/gwt/samples/mail/src/com/google/gwt/sample/mail/client/ Mail.java' [java] [ERROR] Internal compiler error [java] java.lang.RuntimeException: Unable to commit generated files [java] at com.google.gwt.dev.jdt.WebModeCompilerFrontEnd.doFindAdditionalTypesUsingRebinds (WebModeCompilerFrontEnd.java:143) [java] at com.google.gwt.dev.jdt.AbstractCompiler $CompilerImpl.process(AbstractCompiler.java:161) [java] at org.eclipse.jdt.internal.compiler.Compiler.compile (Compiler.java:444) [java] at com.google.gwt.dev.jdt.AbstractCompiler $CompilerImpl.compile(AbstractCompiler.java:84) [java] at com.google.gwt.dev.jdt.AbstractCompiler $CompilerImpl.compile(AbstractCompiler.java:196) [java] at com.google.gwt.dev.jdt.AbstractCompiler $CompilerImpl.access$300(AbstractCompiler.java:70) [java] at com.google.gwt.dev.jdt.AbstractCompiler.compile (AbstractCompiler.java:481) [java] at com.google.gwt.dev.jdt.BasicWebModeCompiler.getCompilationUnitDeclarations (BasicWebModeCompiler.java:113) [java] at com.google.gwt.dev.jdt.WebModeCompilerFrontEnd.getCompilationUnitDeclarations (WebModeCompilerFrontEnd.java:49) [java] at com.google.gwt.dev.jjs.JavaToJavaScriptCompiler.precompile (JavaToJavaScriptCompiler.java:415) [java] at com.google.gwt.dev.jjs.JavaScriptCompiler.precompile (JavaScriptCompiler.java:32) [java] at com.google.gwt.dev.Precompile.precompile (Precompile.java:507) [java] at com.google.gwt.dev.Precompile.precompile (Precompile.java:408) [java] at com.google.gwt.dev.Compiler.run(Compiler.java:194) [java] at com.google.gwt.dev.Compiler$1.run(Compiler.java: 145) [java] at com.google.gwt.dev.CompileTaskRunner.doRun (CompileTaskRunner.java:89) [java] at com.google.gwt.dev.CompileTaskRunner.runWithAppropriateLogger (CompileTaskRunner.java:83) [java] at com.google.gwt.dev.Compiler.main(Compiler.java:152) [java] Caused by: com.google.gwt.core.ext.UnableToCompleteException: (see previous log entries) [java] at com.google.gwt.dev.javac.StandardGeneratorContext.finish (StandardGeneratorContext.java:391) [java] at com.google.gwt.dev.jdt.WebModeCompilerFrontEnd.doFindAdditionalTypesUsingRebinds (WebModeCompilerFrontEnd.java:141) [java] ... 17 more [java] [java] [ERROR] Unexpected [java] java.lang.RuntimeException: Unable to commit generated files [java] at com.google.gwt.dev.jdt.WebModeCompilerFrontEnd.doFindAdditionalTypesUsingRebinds (WebModeCompilerFrontEnd.java:143) [java] at com.google.gwt.dev.jdt.AbstractCompiler $CompilerImpl.process(AbstractCompiler.java:161) [java] at org.eclipse.jdt.internal.compiler.Compiler.compile (Compiler.java:444) [java] at com.google.gwt.dev.jdt.AbstractCompiler $CompilerImpl.compile(AbstractCompiler.java:84) [java] at com.google.gwt.dev.jdt.AbstractCompiler $CompilerImpl.compile(AbstractCompiler.java:196) [java] at com.google.gwt.dev.jdt.AbstractCompiler $CompilerImpl.access$300(AbstractCompiler.java:70) [java] at com.google.gwt.dev.jdt.AbstractCompiler.compile (AbstractCompiler.java:481) [java] at com.google.gwt.dev.jdt.BasicWebModeCompiler.getCompilationUnitDeclarations (BasicWebModeCompiler.java:113) [java] at
[gwt-contrib] Re: Can't build trunk
You might also need to do an 'ant clean' after recent updates. Thanks, John LaBanca jlaba...@google.com On Sun, Oct 4, 2009 at 1:27 PM, tfga thiago...@gmail.com wrote: Thank you for you reply, Eric. I was launching ant from within Eclipse. I ran it under cygwin and got a different error (below). I'll try to run it under cmd.exe, as you suggested. gwtc: [java] Compiling module com.google.gwt.sample.mail.Mail [java]Scanning for additional dependencies: file:/C:/Documents %20and%20Settings/tfga/workspace/gwt/samples/mail/src/com/google/gwt/ sample/mail/client/Mail.java [java] Adding '2' new generated units [java] Validating newly compiled units [java] Removing units with errors [java][ERROR] Errors in 'transient source for com.google.gwt.sample.mail.client.Mail_BinderImpl' [java] [ERROR] Line 20: The method addNorth (Widget, double) in the type DockLayoutPanel is not applicable for the arguments (TopPanel, int, int) [java] [ERROR] Line 21: The method addWest (Widget, double) in the type DockLayoutPanel is not applicable for the arguments (Shortcuts, int, int) [java] [ERROR] Line 22: The method addNorth (Widget, double) in the type DockLayoutPanel is not applicable for the arguments (MailList, int, int) [java] See snapshot: c:\DOCUME~1\tfga \CONFIG~1\Temp \com.google.gwt.sample.mail.client.Mail_BinderImpl2569137898788811986.java [java] [ERROR] Unable to find recently-generated type 'com.google.gwt.sample.mail.client.Mail_BinderImpl [java][ERROR] Errors in 'file:/C:/Documents%20and%20Settings/ tfga/workspace/gwt/samples/mail/src/com/google/gwt/sample/mail/client/ Mail.java' [java] [ERROR] Internal compiler error [java] java.lang.RuntimeException: Unable to commit generated files [java] at com.google.gwt.dev.jdt.WebModeCompilerFrontEnd.doFindAdditionalTypesUsingRebinds (WebModeCompilerFrontEnd.java:143) [java] at com.google.gwt.dev.jdt.AbstractCompiler $CompilerImpl.process(AbstractCompiler.java:161) [java] at org.eclipse.jdt.internal.compiler.Compiler.compile (Compiler.java:444) [java] at com.google.gwt.dev.jdt.AbstractCompiler $CompilerImpl.compile(AbstractCompiler.java:84) [java] at com.google.gwt.dev.jdt.AbstractCompiler $CompilerImpl.compile(AbstractCompiler.java:196) [java] at com.google.gwt.dev.jdt.AbstractCompiler $CompilerImpl.access$300(AbstractCompiler.java:70) [java] at com.google.gwt.dev.jdt.AbstractCompiler.compile (AbstractCompiler.java:481) [java] at com.google.gwt.dev.jdt.BasicWebModeCompiler.getCompilationUnitDeclarations (BasicWebModeCompiler.java:113) [java] at com.google.gwt.dev.jdt.WebModeCompilerFrontEnd.getCompilationUnitDeclarations (WebModeCompilerFrontEnd.java:49) [java] at com.google.gwt.dev.jjs.JavaToJavaScriptCompiler.precompile (JavaToJavaScriptCompiler.java:415) [java] at com.google.gwt.dev.jjs.JavaScriptCompiler.precompile (JavaScriptCompiler.java:32) [java] at com.google.gwt.dev.Precompile.precompile (Precompile.java:507) [java] at com.google.gwt.dev.Precompile.precompile (Precompile.java:408) [java] at com.google.gwt.dev.Compiler.run(Compiler.java:194) [java] at com.google.gwt.dev.Compiler$1.run(Compiler.java: 145) [java] at com.google.gwt.dev.CompileTaskRunner.doRun (CompileTaskRunner.java:89) [java] at com.google.gwt.dev.CompileTaskRunner.runWithAppropriateLogger (CompileTaskRunner.java:83) [java] at com.google.gwt.dev.Compiler.main(Compiler.java:152) [java] Caused by: com.google.gwt.core.ext.UnableToCompleteException: (see previous log entries) [java] at com.google.gwt.dev.javac.StandardGeneratorContext.finish (StandardGeneratorContext.java:391) [java] at com.google.gwt.dev.jdt.WebModeCompilerFrontEnd.doFindAdditionalTypesUsingRebinds (WebModeCompilerFrontEnd.java:141) [java] ... 17 more [java] [java] [ERROR] Unexpected [java] java.lang.RuntimeException: Unable to commit generated files [java] at com.google.gwt.dev.jdt.WebModeCompilerFrontEnd.doFindAdditionalTypesUsingRebinds (WebModeCompilerFrontEnd.java:143) [java] at com.google.gwt.dev.jdt.AbstractCompiler $CompilerImpl.process(AbstractCompiler.java:161) [java] at org.eclipse.jdt.internal.compiler.Compiler.compile (Compiler.java:444) [java] at com.google.gwt.dev.jdt.AbstractCompiler $CompilerImpl.compile(AbstractCompiler.java:84) [java] at com.google.gwt.dev.jdt.AbstractCompiler $CompilerImpl.compile(AbstractCompiler.java:196) [java] at com.google.gwt.dev.jdt.AbstractCompiler $CompilerImpl.access$300(AbstractCompiler.java:70) [java] at com.google.gwt.dev.jdt.AbstractCompiler.compile
[gwt-contrib] Re: Can't build trunk
Sorry. I still get the same thing :( On Oct 4, 5:57 pm, John LaBanca jlaba...@google.com wrote: You might also need to do an 'ant clean' after recent updates. Thanks, John LaBanca jlaba...@google.com On Sun, Oct 4, 2009 at 1:27 PM, tfga thiago...@gmail.com wrote: Thank you for you reply, Eric. I was launching ant from within Eclipse. I ran it under cygwin and got a different error (below). I'll try to run it under cmd.exe, as you suggested. gwtc: [java] Compiling module com.google.gwt.sample.mail.Mail [java] Scanning for additional dependencies: file:/C:/Documents %20and%20Settings/tfga/workspace/gwt/samples/mail/src/com/google/gwt/ sample/mail/client/Mail.java [java] Adding '2' new generated units [java] Validating newly compiled units [java] Removing units with errors [java] [ERROR] Errors in 'transient source for com.google.gwt.sample.mail.client.Mail_BinderImpl' [java] [ERROR] Line 20: The method addNorth (Widget, double) in the type DockLayoutPanel is not applicable for the arguments (TopPanel, int, int) [java] [ERROR] Line 21: The method addWest (Widget, double) in the type DockLayoutPanel is not applicable for the arguments (Shortcuts, int, int) [java] [ERROR] Line 22: The method addNorth (Widget, double) in the type DockLayoutPanel is not applicable for the arguments (MailList, int, int) [java] See snapshot: c:\DOCUME~1\tfga \CONFIG~1\Temp \com.google.gwt.sample.mail.client.Mail_BinderImpl2569137898788811986.java [java] [ERROR] Unable to find recently-generated type 'com.google.gwt.sample.mail.client.Mail_BinderImpl [java] [ERROR] Errors in 'file:/C:/Documents%20and%20Settings/ tfga/workspace/gwt/samples/mail/src/com/google/gwt/sample/mail/client/ Mail.java' [java] [ERROR] Internal compiler error [java] java.lang.RuntimeException: Unable to commit generated files [java] at com.google.gwt.dev.jdt.WebModeCompilerFrontEnd.doFindAdditionalTypesUsingRebinds (WebModeCompilerFrontEnd.java:143) [java] at com.google.gwt.dev.jdt.AbstractCompiler $CompilerImpl.process(AbstractCompiler.java:161) [java] at org.eclipse.jdt.internal.compiler.Compiler.compile (Compiler.java:444) [java] at com.google.gwt.dev.jdt.AbstractCompiler $CompilerImpl.compile(AbstractCompiler.java:84) [java] at com.google.gwt.dev.jdt.AbstractCompiler $CompilerImpl.compile(AbstractCompiler.java:196) [java] at com.google.gwt.dev.jdt.AbstractCompiler $CompilerImpl.access$300(AbstractCompiler.java:70) [java] at com.google.gwt.dev.jdt.AbstractCompiler.compile (AbstractCompiler.java:481) [java] at com.google.gwt.dev.jdt.BasicWebModeCompiler.getCompilationUnitDeclarations (BasicWebModeCompiler.java:113) [java] at com.google.gwt.dev.jdt.WebModeCompilerFrontEnd.getCompilationUnitDeclarations (WebModeCompilerFrontEnd.java:49) [java] at com.google.gwt.dev.jjs.JavaToJavaScriptCompiler.precompile (JavaToJavaScriptCompiler.java:415) [java] at com.google.gwt.dev.jjs.JavaScriptCompiler.precompile (JavaScriptCompiler.java:32) [java] at com.google.gwt.dev.Precompile.precompile (Precompile.java:507) [java] at com.google.gwt.dev.Precompile.precompile (Precompile.java:408) [java] at com.google.gwt.dev.Compiler.run(Compiler.java:194) [java] at com.google.gwt.dev.Compiler$1.run(Compiler.java: 145) [java] at com.google.gwt.dev.CompileTaskRunner.doRun (CompileTaskRunner.java:89) [java] at com.google.gwt.dev.CompileTaskRunner.runWithAppropriateLogger (CompileTaskRunner.java:83) [java] at com.google.gwt.dev.Compiler.main(Compiler.java:152) [java] Caused by: com.google.gwt.core.ext.UnableToCompleteException: (see previous log entries) [java] at com.google.gwt.dev.javac.StandardGeneratorContext.finish (StandardGeneratorContext.java:391) [java] at com.google.gwt.dev.jdt.WebModeCompilerFrontEnd.doFindAdditionalTypesUsingRebinds (WebModeCompilerFrontEnd.java:141) [java] ... 17 more [java] [java] [ERROR] Unexpected [java] java.lang.RuntimeException: Unable to commit generated files [java] at com.google.gwt.dev.jdt.WebModeCompilerFrontEnd.doFindAdditionalTypesUsingRebinds (WebModeCompilerFrontEnd.java:143) [java] at com.google.gwt.dev.jdt.AbstractCompiler $CompilerImpl.process(AbstractCompiler.java:161) [java] at org.eclipse.jdt.internal.compiler.Compiler.compile (Compiler.java:444) [java] at com.google.gwt.dev.jdt.AbstractCompiler $CompilerImpl.compile(AbstractCompiler.java:84) [java] at com.google.gwt.dev.jdt.AbstractCompiler
[gwt-contrib] Re: Can't build trunk
Ok, I didn't mean to mislead you, as it turns out, I was able to get the trunk build to complete successfully under cygwin on Vista svn up svn st (no files appeared modified, if they do, try svn -R revert ./) ant clean ant On Sun, Oct 4, 2009 at 8:38 PM, tfga thiago...@gmail.com wrote: Sorry. I still get the same thing :( On Oct 4, 5:57 pm, John LaBanca jlaba...@google.com wrote: You might also need to do an 'ant clean' after recent updates. Thanks, John LaBanca jlaba...@google.com On Sun, Oct 4, 2009 at 1:27 PM, tfga thiago...@gmail.com wrote: Thank you for you reply, Eric. I was launching ant from within Eclipse. I ran it under cygwin and got a different error (below). I'll try to run it under cmd.exe, as you suggested. gwtc: [java] Compiling module com.google.gwt.sample.mail.Mail [java]Scanning for additional dependencies: file:/C:/Documents %20and%20Settings/tfga/workspace/gwt/samples/mail/src/com/google/gwt/ sample/mail/client/Mail.java [java] Adding '2' new generated units [java] Validating newly compiled units [java] Removing units with errors [java][ERROR] Errors in 'transient source for com.google.gwt.sample.mail.client.Mail_BinderImpl' [java] [ERROR] Line 20: The method addNorth (Widget, double) in the type DockLayoutPanel is not applicable for the arguments (TopPanel, int, int) [java] [ERROR] Line 21: The method addWest (Widget, double) in the type DockLayoutPanel is not applicable for the arguments (Shortcuts, int, int) [java] [ERROR] Line 22: The method addNorth (Widget, double) in the type DockLayoutPanel is not applicable for the arguments (MailList, int, int) [java] See snapshot: c:\DOCUME~1\tfga \CONFIG~1\Temp \com.google.gwt.sample.mail.client.Mail_BinderImpl2569137898788811986.java [java] [ERROR] Unable to find recently-generated type 'com.google.gwt.sample.mail.client.Mail_BinderImpl [java][ERROR] Errors in 'file:/C:/Documents%20and%20Settings/ tfga/workspace/gwt/samples/mail/src/com/google/gwt/sample/mail/client/ Mail.java' [java] [ERROR] Internal compiler error [java] java.lang.RuntimeException: Unable to commit generated files [java] at com.google.gwt.dev.jdt.WebModeCompilerFrontEnd.doFindAdditionalTypesUsingRebinds (WebModeCompilerFrontEnd.java:143) [java] at com.google.gwt.dev.jdt.AbstractCompiler $CompilerImpl.process(AbstractCompiler.java:161) [java] at org.eclipse.jdt.internal.compiler.Compiler.compile (Compiler.java:444) [java] at com.google.gwt.dev.jdt.AbstractCompiler $CompilerImpl.compile(AbstractCompiler.java:84) [java] at com.google.gwt.dev.jdt.AbstractCompiler $CompilerImpl.compile(AbstractCompiler.java:196) [java] at com.google.gwt.dev.jdt.AbstractCompiler $CompilerImpl.access$300(AbstractCompiler.java:70) [java] at com.google.gwt.dev.jdt.AbstractCompiler.compile (AbstractCompiler.java:481) [java] at com.google.gwt.dev.jdt.BasicWebModeCompiler.getCompilationUnitDeclarations (BasicWebModeCompiler.java:113) [java] at com.google.gwt.dev.jdt.WebModeCompilerFrontEnd.getCompilationUnitDeclarations (WebModeCompilerFrontEnd.java:49) [java] at com.google.gwt.dev.jjs.JavaToJavaScriptCompiler.precompile (JavaToJavaScriptCompiler.java:415) [java] at com.google.gwt.dev.jjs.JavaScriptCompiler.precompile (JavaScriptCompiler.java:32) [java] at com.google.gwt.dev.Precompile.precompile (Precompile.java:507) [java] at com.google.gwt.dev.Precompile.precompile (Precompile.java:408) [java] at com.google.gwt.dev.Compiler.run(Compiler.java:194) [java] at com.google.gwt.dev.Compiler$1.run(Compiler.java: 145) [java] at com.google.gwt.dev.CompileTaskRunner.doRun (CompileTaskRunner.java:89) [java] at com.google.gwt.dev.CompileTaskRunner.runWithAppropriateLogger (CompileTaskRunner.java:83) [java] at com.google.gwt.dev.Compiler.main(Compiler.java:152) [java] Caused by: com.google.gwt.core.ext.UnableToCompleteException: (see previous log entries) [java] at com.google.gwt.dev.javac.StandardGeneratorContext.finish (StandardGeneratorContext.java:391) [java] at com.google.gwt.dev.jdt.WebModeCompilerFrontEnd.doFindAdditionalTypesUsingRebinds (WebModeCompilerFrontEnd.java:141) [java] ... 17 more [java] [java] [ERROR] Unexpected [java] java.lang.RuntimeException: Unable to commit generated files [java] at com.google.gwt.dev.jdt.WebModeCompilerFrontEnd.doFindAdditionalTypesUsingRebinds (WebModeCompilerFrontEnd.java:143)
[gwt-contrib] Re: Can't build trunk
Going back to some of your original questions: 1. The default behavior is to build cross-platform. If you only care about the platform you're on, there's a *-one family of targets, and to leave things like samples and tools behind, a *-dev family. Try ant dist-dev to make a one-platform distribution without samples or tools, although you might find you actually *want* especially the tools. But most of us don't iterate on them as often, which is why they're left out from those rules. Or, use dist-one if you do want them. 2. As a hack to your svn issue, if you just pre-define the ant properties it's supposed to set from svn info and svnversion, the SvnInfoTask will skip over the work (and thus skip not finding svn). That'd look something like: - ant -dgwt.svnrev=tr...@5678 dist-one 3. There's no reason cygwin shouldn't work for you, but you don't need it either. There's a perfectly good native Windows svn at http://www.collab.net/downloads/subversion/. If you're already using cygwin, e.g. for git, of course, then as noted it *should* have worked fine... we need[*] a svnversion and svn executable on the command line, but we don't care which port or environment. 4. Your LONG compiler errors in Browser are screwy; as Eric says, we don't see them... and we're desparately trying to retire our swt dependency anyway. But at a guess, I suspect you've got different Eclipse jars on your classpath than you should, especially if you're building from some Eclipse. I haven't done an exhaustive check in all the jars, but in $GWT_TOOLS/lib/eclipse/org.eclipse.swt.gtk-linux-3.2.1.jar I see only the ...internal.gtk.LONG class, *not* the internal.LONG variant. I suspect you're getting a more modern Eclipse jar, and that they must have refactored it up or somesuch. Ant -v will report the classpath; I suspect you'll find a stray jar from outside the GWT and GWT_TOOLS hierarchies which is messing you up. (My own ant -v is below, but you shouldn't need to do the 1:1 matching; just look for something from the wrong directories!) - [gwt.javac] 'C:\Documents and Settings\fabbott\My Documents\GWTs\collections\build\out\dev\linux\bin;C:\Documents and Settings\fabbott\My Documents\GWTs\tools\lib\eclipse\org.eclipse.swt.gtk-linux-3.2.1.jar;C:\Documents and Settings\fabbott\My Documents\GWTs\collections\build\out\dev\core\bin;C:\Documents and Settings\fabbott\My Documents\GWTs\collections\build\out\dev\core\alldeps.jar;C:\Program Files\apache-ant-1.7.1\lib\ant-launcher.jar;C:\Program Files\apache-ant-1.7.1\lib\ant-antlr.jar;C:\Program Files\apache-ant-1.7.1\lib\ant-apache-bcel.jar;C:\Program Files\apache-ant-1.7.1\lib\ant-apache-bsf.jar;C:\Program Files\apache-ant-1.7.1\lib\ant-apache-log4j.jar;C:\Program Files\apache-ant-1.7.1\lib\ant-apache-oro.jar;C:\Program Files\apache-ant-1.7.1\lib\ant-apache-regexp.jar;C:\Program Files\apache-ant-1.7.1\lib\ant-apache-resolver.jar;C:\Program Files\apache-ant-1.7.1\lib\ant-commons-logging.jar;C:\Program Files\apache-ant-1.7.1\lib\ant-commons-net.jar;C:\Program Files\apache-ant-1.7.1\lib\ant-contrib-1.0b3.jar;C:\Program Files\apache-ant-1.7.1\lib\ant-jai.jar;C:\Program Files\apache-ant-1.7.1\lib\ant-javamail.jar;C:\Program Files\apache-ant-1.7.1\lib\ant-jdepend.jar;C:\Program Files\apache-ant-1.7.1\lib\ant-jmf.jar;C:\Program Files\apache-ant-1.7.1\lib\ant-jsch.jar;C:\Program Files\apache-ant-1.7.1\lib\ant-junit.jar;C:\Program Files\apache-ant-1.7.1\lib\ant-netrexx.jar;C:\Program Files\apache-ant-1.7.1\lib\ant-nodeps.jar;C:\Program Files\apache-ant-1.7.1\lib\ant-starteam.jar;C:\Program Files\apache-ant-1.7.1\lib\ant-stylebook.jar;C:\Program Files\apache-ant-1.7.1\lib\ant-swing.jar;C:\Program Files\apache-ant-1.7.1\lib\ant-testutil.jar;C:\Program Files\apache-ant-1.7.1\lib\ant-trax.jar;C:\Program Files\apache-ant-1.7.1\lib\ant-weblogic.jar;C:\Program Files\apache-ant-1.7.1\lib\ant.jar;C:\Program Files\apache-ant-1.7.1\lib\xercesImpl.jar;C:\Program Files\apache-ant-1.7.1\lib\xml-apis.jar;c:\Progra~1\Java\jdk1.6.0_14\lib\tools.jar' Hope those help! [*] there's some suggestion to use SvnKit instead, because people keep updating graphical tools like TortoiseSVN, and then getting newer .svn directories than their command-line tools can handle and having errors because of that. I've resisted SvnKit, though, because I think it just adds a third way for things to get skewed... On Sun, Oct 4, 2009 at 8:38 PM, tfga thiago...@gmail.com wrote: Sorry. I still get the same thing :( On Oct 4, 5:57 pm, John LaBanca jlaba...@google.com wrote: You might also need to do an 'ant clean' after recent updates. Thanks, John LaBanca jlaba...@google.com On Sun, Oct 4, 2009 at 1:27 PM, tfga
