As and when new and radical features are introduced, it would go a long way
if a sample project that implements such concepts were provided. Case in
point is that of modules, web modules, EJB modules.
There are several hearty souls amongst us EAPers that will slave endless
hours trying to figure out how the heck Feature-X is supposed to be used,
why did my source directory just vanish, why does this file have a red icon,
why, why, why .... It also takes us far away from the task at hand. Wait, I
hear you: That is the price of being on the bleeding edge...but is it?
I realize that providing help for an tool that is in a fluid state is not a
productive use of JetBrainers time. However since they surely have run
tests to dry run these new features, it shouldn't be a monumental effort to
package a samples directory along with the installation; most open-source
projects follow this model. Although your particular project may not
exactly map totally to the sample, at least it will get you started.
I am a couple of hours into my expedition into Modules and have
-- Fiddled around with the settings
-- Scoured EAP and J2EE newsgroups
-- Read the wiki
-- Read the EAP change log
and don't have much to show for it. I have a good mind to ditch it since I
use Maven and don't depend on IDEA for my builds. However, I am plugging
away in anticipation of the epiphany and the hope that the suggested
integration with tools implies auto-generation of code/descriptors; in other
words a simplification of development effort.