Intellij does not work with GWT 1.5 rc1 ...

Google just released GWT 1.5 rc1 unfortunately the changes cause the GWT support in Intellij to be broken. I reckon that rc1 is as good as final release and if it is broken now, do expect it to broken when it release. Even when start from a fresh project manned to create for GWT 1.5, the project fail to compile giving error such as

Unable to find type

among other errors. I find it a little peculiar that GWT that quote to use IDE as its main advantage couldn't coordinate with IDE vendor to ensure latest test build run well with popular IDE...

What is the point of releasing rc1 when no IDE is able to support it and hence no one going to test it ? Isn't that akin to having a Porsche with a punctured tyre ?

Hope that Jetbrain seriously look into this issue and see if they can develop a fix for Intellij 7...

10 comments
Comment actions Permalink

GWT 1.5 support seems to be on the roadmap for IDEA 8.0 (Diana), but I haven't given the EAP Builds a try to see if the GWT 1.5 release candidate works yet or not.

The bummer is that most plugins won't work with Diana without significant modification, so it may not be too useful yet. Also, the EAP releases for IDEA 7.0.x make no mention of GWT 1.5 at all. I'd really like to dive in and use GWT 1.5, but it looks like I'll be doing so without the help of my IDE for a while.

Anyone from JetBrains that can give us some visibility into the future plans, beyond what's stated in the roadmap?

0
Comment actions Permalink

Hello Peter,

GWT 1.5 support seems to be [on the roadmap for IDEA 8.0
(Diana)|http://www.jetbrains.net/confluence/display/IDEADEV/IDEA8.0T
echnology+Roadmap], but I haven't given the [EAP
Builds|http://www.jetbrains.net/confluence/display/IDEADEV/Diana+EAP]
a try to see if the GWT 1.5 release candidate works yet or not.

The bummer is that most plugins won't work with Diana without
significant modification, so it may not be too useful yet. Also, the
[EAP releases for IDEA
7.0.x|http://www.jetbrains.net/confluence/display/IDEADEV/Selena+EAP]
make no mention of GWT 1.5 at all. I'd really like to dive in and use
GWT 1.5, but it looks like I'll be doing so without the help of my IDE
for a while.

Anyone from JetBrains that can give us some visibility into the future
plans, beyond what's stated in the roadmap?


Diana EAP builds already include some new features for GWT 1.5 support (mostly
helpers for converting the old javadoc declarations to annotations). We don't
have any plans to backport them to Selena. We'll investigate why Selena doesn't
work with the 1.5 RC build (it used to work with older 1.5 builds) and try
to fix it so that at least the existing functionality works.

--
Dmitry Jemerov
Development Lead
JetBrains, Inc.
http://www.jetbrains.com/
"Develop with Pleasure!"


0
Comment actions Permalink

Hello Dmitry,

Great news. Thanks for the quick update, and I'm glad to hear that the existing functionality for GWT will still be supported in the Selena product line. Looking forward to the new stuff in Diana as soon as I find some spare time.


Peter

0
Comment actions Permalink

I cannot reproduce your problem. IDEA 7 works fine with GWT 1.5 rc1 for
me. Could you please give exact steps to reproduce the problem and
attach your iml/ipr files?

Google just released GWT 1.5 rc1 unfortunately the changes cause the GWT support in Intellij to be broken. I reckon that rc1 is as good as final release and if it is broken now, do expect it to broken when it release. Even when start from a fresh project manned to create for GWT 1.5, the project fail to compile giving error such as

Unable to find type

among other errors. I find it a little peculiar that GWT that quote to use IDE as its main advantage couldn't coordinate with IDE vendor to ensure latest test build run well with popular IDE...

What is the point of releasing rc1 when no IDE is able to support it and hence no one going to test it ? Isn't that akin to having a Porsche with a punctured tyre ?

Hope that Jetbrain seriously look into this issue and see if they can develop a fix for Intellij 7...



--
Nikolay Chashnikov
Software Developer
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

0
Comment actions Permalink

Hello.

I also have problems using the GWT rc1 with IntelliJ 7. So far I used the trunk of GWT without a problem.

It gives me the following error when using String:
Class java.lang.String is not presented in the JRE Emulation Library so it cannot be used in client code

When building the project, I get the following errors:
Error:An internal compiler exception occurred
Error:at com.google.gwt.dev.jjs.ast.JVisitor.translateException(JVisitor.java:538)
Error:at com.google.gwt.dev.jjs.ast.JVisitor.doTraverse(JVisitor.java:529)
Error:at com.google.gwt.dev.jjs.ast.JVisitor.doAccept(JVisitor.java:509)
Error:at com.google.gwt.dev.jjs.ast.JVisitor.accept(JVisitor.java:65)
Error:at com.google.gwt.dev.jjs.ast.JClassLiteral.traverse(JClassLiteral.java:127)
Error:at com.google.gwt.dev.jjs.ast.JVisitor.doTraverse(JVisitor.java:527)
Error:at com.google.gwt.dev.jjs.ast.JReturnStatement.traverse(JReturnStatement.java:39)
Error:at com.google.gwt.dev.jjs.ast.JVisitor.doAcceptWithInsertRemove(JVisitor.java:521)
Error:at com.google.gwt.dev.jjs.ast.JVisitor.acceptWithInsertRemove(JVisitor.java:81)
Error:at com.google.gwt.dev.jjs.ast.JBlock.traverse(JBlock.java:36)
Error:at com.google.gwt.dev.jjs.ast.JVisitor.accept(JVisitor.java:73)
Error:at com.google.gwt.dev.jjs.ast.JMethodBody.traverse(JMethodBody.java:52)
Error:at com.google.gwt.dev.jjs.ast.JVisitor.accept(JVisitor.java:69)
Error:at com.google.gwt.dev.jjs.ast.JMethod.traverse(JMethod.java:194)
Error:at com.google.gwt.dev.jjs.ast.JClassType.traverse(JClassType.java:62)
Error:at com.google.gwt.dev.jjs.ast.JVisitor.doAccept(JVisitor.java:515)
Error:at com.google.gwt.dev.jjs.ast.JVisitor.accept(JVisitor.java:77)
Error:at com.google.gwt.dev.jjs.ast.JProgram.traverse(JProgram.java:799)
Error:at com.google.gwt.dev.jjs.impl.TypeTightener.execImpl(TypeTightener.java:780)
Error:at com.google.gwt.dev.jjs.impl.TypeTightener.exec(TypeTightener.java:722)
Error:at com.google.gwt.dev.jjs.JavaToJavaScriptCompiler.compile(JavaToJavaScriptCompiler.java:398)
Error:at com.google.gwt.dev.GWTCompiler.realizePermutation(GWTCompiler.java:511)
Error:at com.google.gwt.dev.GWTCompiler.compilePermutations(GWTCompiler.java:442)
Error:at com.google.gwt.dev.GWTCompiler.distill(GWTCompiler.java:358)
Error:at com.google.gwt.dev.GWTCompiler.run(GWTCompiler.java:564)
Error:at com.google.gwt.dev.GWTCompiler.run(GWTCompiler.java:554)
Error:at com.google.gwt.dev.GWTCompiler.main(GWTCompiler.java:214)
Error:at java.util.AbstractList$Itr.next(AbstractList.java:350)
Error:at com.google.gwt.dev.jjs.impl.TypeTightener$RecordVisitor.endVisit(TypeTightener.java:231)
Error:at com.google.gwt.dev.jjs.ast.JMethodCall.traverse(JMethodCall.java:124)
Error:: Class.createForEnum("de.lmu.edu.mitschau.client.", "LessonerTimeLineData$ElementKeys") Error:: LessonerTimeLineData$ElementKeys.class Error:: return LessonerTimeLineData$ElementKeys.class Error:: { Error:: public final Class getClass(); Error:at LessonerTimeLineData.java(18): final class LessonerTimeLineData$ElementKeys extends Enum Error:: ]]>

0
Comment actions Permalink

Hello.

I figured out the problem about the missing String JRE emulation. There was the wrong path in the module settings for the GWT installation directory.

But the other error persits. I found out, that it is with GWT trunk revision 2489 the problem begins.

So, checking out revision 2488 from GWT trunk, compile with ant and setting the correct GWT installation folder and the path to the jar files works perfectly.

Doing the same thing with revision 2489 results in build errors like listet above.

I am using IntelliJ 7 on Ubuntu 8.0.4.

Maybe this helps to find where the problem comes from.


Thanks,
Michael Vogt

Edited by: Michael Vogt on Jun 2, 2008 5:33 PM

0
Comment actions Permalink

The "internal compiler exception" problem is caused by GWT itself (see
http://code.google.com/p/google-web-toolkit/issues/detail?id=1659).

Hello.

I figured out the problem about the missing String JRE emulation. There was the wrong path in the module settings for the GWT installation directory.

But the other error persits. I found out, that it is with GWT trunk revision 2489 the problem begins.

So, checking out revision 2488 from GWT trunk, compile with ant and setting the correct GWT installation folder and the path to the jar files works perfectly.

Doing the same thing with revision 2489 results in build errors like listet above.

Maybe this helps to find where the problem comes from.


Thanks,
Michael Vogt



--
Nikolay Chashnikov
Software Developer
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

0
Comment actions Permalink

Hello Nikolay.

You are correct, this is not an IntelliJ problem. I am sorry for the noise and for hichacking this bugreport.

The gwt issue you linked to is not related to the problem, though. I found out that the usage of EnumMap caused the problem.

I replaced the use of EnumMap with HashMap and all is working again.


Greetings,
Michael Vogt

Edited by: Michael Vogt on Jun 5, 2008 1:11 PM

0
Comment actions Permalink

Hi,

On Mac OS X 1.5 using GWT 1.5 rc1 I am getting this error when I try to run inside of IDEA 7.0.3

Unable to load required native library 'gwt-ll'. Detailed error:
/Volumes/mono/personal/dev/gwt-mac-1.5.0/libgwt-ll.jnilib: )

Your GWT installation may be corrupt
Exception in thread "main" java.lang.UnsatisfiedLinkError: Unable to load required native library 'gwt-ll'. Detailed error:
/Volumes/mono/personal/dev/gwt-mac-1.5.0/libgwt-ll.jnilib: )

Your GWT installation may be corrupt
at com.google.gwt.dev.shell.LowLevel.init(LowLevel.java:107)
at com.google.gwt.dev.shell.mac.LowLevelSaf.init(LowLevelSaf.java:130)
at com.google.gwt.dev.BootStrapPlatform.init(BootStrapPlatform.java:34)
at com.google.gwt.dev.GWTShell.main(GWTShell.java:355)

works OK from the command line.

Should I try a EAP build for better results?

Thanks in advance,

Spencer

0
Comment actions Permalink

OK, this is another non IDEA issue with the GWT.

This time it has to due with Java 6 on Mac OX 1.5 being 64 byte only meaning it can't use native libs that aren't 32 byte like gwt-ll

see:

http://code.google.com/p/google-web-toolkit/issues/detail?id=2507

The workaround is to use Java 5 not Java 6 for Mac OS X 1.5 GWT projects.

--- details from link above:

Found in GWT Release: Mac 1.5.0

Detailed description:
When Java Preferences are set to use Java SE 6 (1.6.0_05) on Leopard (OS X
10.5.3), compiles on projects seem to work, while running in hosted mode
doesn't. Running the Hello application in the samples directory after a
successful compile yeilds:

./Hello-shell
Unable to load required native library 'gwt-ll'. Detailed error:
/Library/gwt-mac-1.5.0/libgwt-ll.jnilib: )

Your GWT installation may be corrupt
Exception in thread "main" java.lang.UnsatisfiedLinkError: Unable to load
required native library 'gwt-ll'. Detailed error:
/Library/gwt-mac-1.5.0/libgwt-ll.jnilib: )

Your GWT installation may be corrupt
at com.google.gwt.dev.shell.LowLevel.init(LowLevel.java:107)
at com.google.gwt.dev.shell.mac.LowLevelSaf.init(LowLevelSaf.java:130)
at com.google.gwt.dev.BootStrapPlatform.init(BootStrapPlatform.java:34)
at com.google.gwt.dev.GWTShell.main(GWTShell.java:355)



Workaround if you have one:
Switching back to Java SE 5 seems to mitigate the problem.

Links to the relevant GWT Developer Forum posts:
This seems to resemble this issue from a prior version of GWT:
http://code.google.com/p/google-web-toolkit/issues/detail?id=1792
Comment 1 by alex.moffat, Jun 09, 2008
Java 6 on OS X is 64 bit only so I believe hosted mode isn't going to work with Java 6 on OS X until the browser
plugin solution that supports 64 bit JVMs is released. This is unfortunate as there is not a non-64 bit Java 6
solution available for OS X, in contrast to other platforms, so there is no workaround available.

0

Please sign in to leave a comment.