h2. Introduction
Typically when an Eclipse project is shared by different development teams, commit 'Eclipse settings files' could drive to fix them everytime another developer checkout or update the project (unless we synchonize 'eclipse workspaces' over teams).
If you have this problem and want "automatically' ignore eclipse project settings feel free to use the shell below
{noformat}
rm -rf /tmp/.settings
cp .classpath /tmp
cp .project /tmp
cp -R .settings /tmp
svn del .classpath
svn del .project
svn del .settings
svn propset svn:ignore ".classpath
*.log
.project
.settings
target" .
svn commit -m'ignore eclipse settings'
cp /tmp/.classpath .
cp /tmp/.project .
cp -R /tmp/.settings .
{noformat}
Typically when an Eclipse project is shared by different development teams, commit 'Eclipse settings files' could drive to fix them everytime another developer checkout or update the project (unless we synchonize 'eclipse workspaces' over teams).
If you have this problem and want "automatically' ignore eclipse project settings feel free to use the shell below
{noformat}
rm -rf /tmp/.settings
cp .classpath /tmp
cp .project /tmp
cp -R .settings /tmp
svn del .classpath
svn del .project
svn del .settings
svn propset svn:ignore ".classpath
*.log
.project
.settings
target" .
svn commit -m'ignore eclipse settings'
cp /tmp/.classpath .
cp /tmp/.project .
cp -R /tmp/.settings .
{noformat}