GWT 1.5 doesn't compile module with 7.0.3

I can't find much about GWT 1.5 support in IDEA 7 except for 1 thread of someone who couldn't get it to work and someone else saying "it works fine for me". Well, it doesn't work fine for me. I was trying IDEA again because I love the JavaScript editor. It's the best around and I thought maybe I could port over the work I've been doing in eclipse so I get the best of all worlds. No such luck.

I'm using GWT 1.5 trunk for the Javascript overlays. It no work in the GWT studio plugin, though. I'm not sure exactly what it's (not) doing, but it acts like it starts to compile, but quickly dies with no exceptions or anything. I have no idea what's not working because there's no indication of an error, there's just no output files.

I know this has worked before because I was using 1.5 rc1 before switching to trunk. Combined with my bad experiences today with plugin installation not working, I'm wondering whether I have time to spend troubleshooting this. I can't say they're related, but it seems like too much of a coincidence.

Is there something else going on in a plugin update or something that are causing issues and everyone's just keeping mum about it? I even started with a fresh install of IDEA and things haven't been working.

I'm started to get frustrated...

5 comments
Avatar
Nikolay Chashnikov
Comment actions Permalink

Please replace your /bin/log.xml file by the attached one, reproduce the problem and post here ]]>/log/idea.log file.


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



Attachment(s):
log.xml
0
Comment actions Permalink

The compiled files appear in the ~/Library/Caches directory specified here on the command line, but they are not copied into the out folder or any other place accessible to the application.



Attachment(s):
idea_log.txt
0
Comment actions Permalink

Thought maybe changing the Groovy version (which fixed my problem with installing plugins) might impact this problem with GWT compile, but it doesn't look like it is. The GWT-generated files are still buried somewhere inside the cache directory rather than being copied into my project output directory (I left the default of $PROJECT/out).

0
Comment actions Permalink

For anyone that comes tripping along this path in the future: it appears that the only way to get your GWT compiler output automatically is to create your module with BOTH GWT and Web facets (you can't add the Web facet later, apparently), even if you're not using a JSP-style web application because you're not using RPC.

If you're using JSON and/or Javascript overlays, forget it. You'll have to set up an ant build task or an external tool (which is horrendously non-portable because you have to hard-code a couple values like module name, not to mention it's a little bit of a pain because you can't hit cmd-f9 and get a build).

I guess all the effort is being put into Diana as far as GWT goes, so I'm downloading the EAP build now and trying that. It'll probably not work for me, though, as I suspect plugin breakage will mean GWT might work, but I'm screwed on anything else!

0
Avatar
Nikolay Chashnikov
Comment actions Permalink

You can configure GWT facet to put generated files into exploded directory of Web facet at any time. Just select GWT facet node in Project Settings
dialog and select an appropriate Web facet in the combobox after label "Package generated files into Web Facet".

However I agree that it's inconvenient to create a Web facet only to get GWT compiler output so I've created a Jira issue "Allow to specify directory
for files generated by GWT compiler" (http://jetbrains.net/jira/browse/IDEADEV-28821).

For anyone that comes tripping along this path in the future: it appears that the only way to get your GWT compiler output automatically is to create your module with BOTH GWT and Web facets (you can't add the Web facet later, apparently), even if you're not using a JSP-style web application because you're not using RPC.

If you're using JSON and/or Javascript overlays, forget it. You'll have to set up an ant build task or an external tool (which is horrendously non-portable because you have to hard-code a couple values like module name, not to mention it's a little bit of a pain because you can't hit cmd-f9 and get a build).

I guess all the effort is being put into Diana as far as GWT goes, so I'm downloading the EAP build now and trying that. It'll probably not work for me, though, as I suspect plugin breakage will mean GWT might work, but I'm screwed on anything else!



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

0

Please sign in to leave a comment.