Support for GWT super-source

I'm building an EE application (IntelliJ 9) with a GWT component, where I need to use the GWT super-source element in my GWT module. That element appears to be supported in GWT modules in external libraries (although the inspections seem partially broken), but I can't figure out how to make it work in a GWT module in my own IntelliJ project.

Basically, IntelliJ acts like the super-source element isn't there, and flags translated classes as being in the wrong directory for the package statement.

So does IntelliJ GWT support authoring of modules using the super-source element, and how do we set it up in the project?

2 comments

Currently IDEA doesn't support 'super-source' tags. Could you please create an issue for that in our tracker (http://youtrack.jetbrains.net/issues/IDEA)?

However you can avoid error messages about 'package' statements if you mark super-source directory as a source root in the module settings.

I'm building an EE application (IntelliJ 9) with a GWT component, where I need to use the GWT super-source element in my GWT module. That element appears to be supported in GWT modules in external libraries (although the inspections seem partially broken), but I can't figure out how to make it work in a GWT module in my own IntelliJ project.

Basically, IntelliJ acts like the super-source element isn't there, and flags translated classes as being in the wrong directory for the package statement.

So does IntelliJ GWT support authoring of modules using the super-source element, and how do we set it up in the project?

---
Original message URL: http://www.jetbrains.net/devnet/message/5260019#5260019



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

0

Thanks for the response. I didn't realise that I could have a source root inside a source root. But then I'm not sure how I can separate out the source roots so that the system doesn't see two different source files for the same class.

In fact, in this case, the class that I'm emulating is in the same project. That is, I'm trying to organise things so that I have one version of a given class running on the server, and a different version of that class (without some of the difficult-to-implement methods) running in the client. The super-source semantics are pretty ugly

I'll raise the issue ticket.

0

Please sign in to leave a comment.