On Jan 5, 2009, at 7:20 AM, Emmanuel Lecharny wrote:
It's way better to let the build tool generate those files. It keeps the project consistent, as you don't commit anything relevant to your own env.
Actually, IDEA uses a project and module file (.ipr and .iml) to store "shared" project settings and maintains environment-specific settings in a workspace file (.iws).
The shared project settings can contain things like standard file templates used by the project, static analysis settings, code style settings, etc. which can help ensure code consistency and best practices. Are there other ways to handle this? Maybe. However, the project files have been in use for a long time with no problems and I'm reluctant to simply remove them.
If a developer really wants to setup their environment in a specific way, they can easily create a custom IDEA project with their own settings. The current IDEA files have been and are still working great for many of the active committers to JSecurity - if there are any problems or errors in these files, please let us know so we can work to resolve any issues.
