The
same goes for IntelliJ - changing the *htm files isn't visible without a
restart. I also changed and saved the Home page class file - still, no
restart or change in page appearance.
In the case of IntelliJ, you need to set the 'exploded' directory to be
the same as
the webapp source directory. This way the changes to any resource would
be picked right away (plus the click tracing level as Bob mentioned
earlier).
Is there some suggested workflow best practice?
This highly depends on the application you wish to develop, on
the size of your team (or developers contributing to your projects), and
also to the level of skills each one has - since for each combination
there are different and more efficient "workflows".
Which IDE works best out of
the box ...
None works best out of the box since these are very complex tools.
I for one like IntelliJ more, but the ClickIDE Eclipse plug-in seems the
most advanced so far and also the most active (I wish Naoki would work
on a IntelliJ plug-in for Click :) ).
and what is the best way to build/work on a project - use the
native WTP and download all the JARS? or can I leverage maven ... or is
there a hybrid approach that I am missing.
This highly depends on what IDE you use, and how you work.
Personally I use ANT with a build.xml very similar to that of Click(and
click examples), or. click-jquery, with a get-deps task that downloads
some of the dependencies, but I also setup the IDE to
be able to do everything by itself too:
- So when I do very small changes, and the server is already running, I
compile from the IDE, so the changes will be picked quickly.
- When I do more important changes or releases, than I'll use ANT.
Also, if this is velocity, is it possible that Velocity will cache these
files? Is there a parameter I can supply that forces velocity not to do
this? I was surprised that Eclipse detected changes to the classpath files -
but not maven's webapp directory.
(looking for solutions other than
zeroturnaround ... but if that is required ....)
It's not required but it helps allot. This "help" isn't a "Click issue"
but a Java (JDK) issue (we all wish SUN/Oracle would simply buy JRebel
and integrate it in the standard JDK ;)).
However, JRebel doesn't work for all Click cases(but for many), since a
"JRebel plug-in" like the one for Tapestry would be required to 100%
work without restarting anything.
regards,
Andrei.
