Hello Jacques, hello Stefan,
we are working on a mid-size application with a team of
10 developers. Most of them are using IntelliJ.
We do store the project and module files (*.ipr, *.iws)
in the CVS. The workspace files (*.iws) however are not
shared via CVS, because they generally contain personal
setting like window positions, the edit history and so
on. Additionally, the workspace file can contain absolute
paths which may or may not exist on the machine where the
checkout is done.
Sadly, both the UnitTest plugin and the KS-SQL plugin do
store some settings in the workspace file which we actually
want to survive check-in / clean / check-out cycles.
UnitTest for example stores the patterns that determine
the class name / testcase name mapping in the iws file.
Isn't this information conceptually part of the project
and should thus be stored in the ipr file?
More or less the same applies to UnitTest's template settings
and options. This stuff should either be part of the project
settings (because they should be consistent among all developers)
or eventually be some kind of global configuration (like the
file templates itsself are).
With KS-SQL we are unable to share database definitions
and driver settings among the team. Both are lost each time
the developer fetches a fresh copy from the cvs. Storing
the database definition in the project settings is obviously
for security reasons not a good idea but there should be the
possibility to define "global" database configurations, similar
to the concept of global libraries. That would make the sql
plugin even more usable in scenarios with many small sub-projects
(because the developer could quickly choose a global database
definition instead of reconfiguring the same settings again and
Last, but not least, a big Thank You! for both plugins. They
help us quite a lot with our daily development tasks.