Is Enable GWT compilation checkbox gone now?

I don't see it anymore in IU 90.94. The main use case is to *disable* compilation, as it takes prohibitely long time on a project, and gwt compilation is done by maven build anyway. It took a lot of fight to bring this switch back (it was removed once), and now again? What's going on? Any reason it was removed?

Thanks,
Andrew

5 comments
Comment actions Permalink

Now GWT compilation is disabled by default. In order to run GWT compiler you need to add "GWT Compiler output" element to an artifact. So GWT
compilation will be performed only if IDEA is building an artifact which includes "GWT Compiler output" item for the corresponding facet.

I don't see it anymore in IU 90.94. The main use case is to disable compilation, as it takes prohibitely long time on a project, and gwt compilation is done by maven build anyway. It took a lot of fight to bring this switch back (it was removed once), and now again? What's going on? Any reason it was removed?

Thanks,
Andrew

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



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

0
Comment actions Permalink

Thanks for clarifying this. I however, think it's counter-intuitive. Wouldn't a checkbox be an expected UI element here? When unchecked - relevant UI group is disabled/greyed out.

0
Comment actions Permalink

I don't think that this checkbox is a good idea. Firstly it duplicates the functionality provided by artifacts. Secondly, if the checkbox is selected
IDEA will run GWT compiler on every compilation even if you're compiling a file which isn't related to GWT.

Thanks for clarifying this. I however, think it's counter-intuitive. Wouldn't a checkbox be an expected UI element here? When unchecked - relevant UI group is disabled/greyed out.

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



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

0
Comment actions Permalink

Ok, let it be, given that artifacts is a new feature and hasn't been finished yet probably. Today artifacts feel a bit standalone from anything else, which doesn't help promoting this new UI section. Does it make sense to link them (like jumping to artifacts from GWT config screen)? Just speculating, it may not make sense, or is already implemented

0
Comment actions Permalink

Artifacts aren't standalone things because they are required to deploy JavaEE application from IDEA. Moreover old JavaEE packaging configuration and
"Build Jar" settings are converted to artifacts automatically when a project is opened in the latest build.

Concerning GWT facet I think it makes sense to add a warning like "GWT Compiler output isn't included into artifact" with the corresponding quickfix
in GWT facet settings editor.

Ok, let it be, given that artifacts is a new feature and hasn't been finished yet probably. Today artifacts feel a bit standalone from anything else, which doesn't help promoting this new UI section. Does it make sense to link them (like jumping to artifacts from GWT config screen)? Just speculating, it may not make sense, or is already implemented

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



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

0

Please sign in to leave a comment.