[ http://jira.codehaus.org/browse/MECLIPSE-71?page=comments#action_60229 ]
Reinhard Poetz commented on MECLIPSE-71: ---------------------------------------- Are there any implications if I don't run "eclipse:clean" before I run "eclipse:eclipse"? Is it possible that the plugin creates some inconsistent Eclipse settings files? If no, I agree with you that deleting isn't necessary. (Although Maven delets a file that it doesn't generate *completly* --> org.eclipse.jdt.core.prefs) I'd propose following cleaning procedure: - eclipse:clean delets all files it generates/manipulates - if after deleting these files, something is left (e.g. .svn directory) the .settings directory is _not_ deleted - if .settings is empty, the .settings directory is deleted too. WDYT? > eclipse:clean delets too much > ----------------------------- > > Key: MECLIPSE-71 > URL: http://jira.codehaus.org/browse/MECLIPSE-71 > Project: Maven 2.x Eclipse Plugin > Type: Bug > Versions: 2.1 > Reporter: Reinhard Poetz > > > If I call eclipse:clean, the complete ".settings" directory is deleted. In my > projects we share some Eclipse settings in our team by adding the .settings > directory to SVN. > This behaviour is unpractical for us as SVN gets confused by the missing > ./settings/.svn directory. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]