Well, it depends on what you think the SCM is for. If it's for sharing, then you may or may not want to share project settings -- it depends on local policy.
But consider a reasonable work cycle: 1. check project A out into a new directory tree 2. develop, test, develop, test... 3. check in updated project A 4. delete directory tree, go work on something else -- time passes -- 5. check project A out into a new directory tree for more work 5a. what the ?!?!?! where are my project settings???? 5b. spend half an hour reconfiguring project before you can work So maybe I want project settings saved, but not shared. Should this be addressed by Maven, the IDE, the SCM, or some combination? -- Mark H. Wood, Lead System Programmer [EMAIL PROTECTED] Typically when a software vendor says that a product is "intuitive" he means the exact opposite.
pgpYLEFqFRpsZ.pgp
Description: PGP signature
