C
cwright
Guest
Mike, Your point is noted. However, if I share .project, then it forces all developers to use the exact same project name. It also forces all developers to have the same natures and facets (they are stored in .project). Same with .dbconnections. This forces all developer to have the same local names and directory structure for their database connections. If you have local dbs, this can cause issues. There are advantages and disadvantages to storing the .project and .dbconnections. You have to weight them for your environment. I think it is wise to export your setting and make that export available to developers in the event they need to restore, but forcing everyone to have the same names and directory structure is a bit rigid for my development style. I do agree with .propath. That should always be the same or you can cause a massive mess during downstream builds Cameron
Continue reading...
Continue reading...