[#IDEA-18674] GWT compilation shouldn't compile all GWT modules.

IDEA: Feedback

GWT compilation shouldn't compile all GWT modules.

Created: 08 Jul 08 18:32 Updated: 02 Oct 08 21:26

Component/s:

GWT Support

Build:

7,757

Description

« Hide

When developping big applications it's quite usual to have dozens of GWT modules.

The classic use case is to make small applications to test few views or small areas of the main application.

When selecting the "Run GWT Compiler on make" on the GWT Facet, all the GWT Modules are compiled which last an unacceptable time.

It should be possible to activate the GWT compilation per GWT module.

All

Comments

Work Log

Change History

Sort Order:

[ Permlink | « Hide ]

Nikolay Chashnikov - 24 Jul 08 16:13

IDEA compiles only GWT modules which sources have been changed since previous compilation. Is it working in your case?

[ Permlink | « Hide ]

Gaetan Zoritchak - 24 Jul 08 16:55

I didn't knew that.

However, it is still a problem when working with lots of modules. A change on one file can impact too much modules. GWT compilation is too slow to work like that.

For the moment, we just deactivate the GWT compilation in idea and use a maven (even if I don't like it) to compile the chosen GWT module.

[ Permlink | « Hide ]

Dave Brown - 02 Oct 08 21:24

With 8823, I am definitely seeing it make all GWT modules on a make. To give a bit of clarity, my module hierarchy has 10-11 modules. Foo, Bar and Baz all inherit from a common Widgets module. While working on Foo, a make command will build Foo, Bar and Baz as well. these modules are unrelated, so they should need to be built. I realize that changing Widgets may require all modules that inherit from it to be built.

[ Permlink | « Hide ]

Dave Brown - 02 Oct 08 21:26

More clarification, which I am trying to nail down. It isn't necessarily any change in Foo that triggers the full build. Trying to figure out what it is with a little experimentation.