[ http://jira.codehaus.org/browse/MECLIPSE-71?page=comments#action_59893 ]
Reinhard Poetz commented on MECLIPSE-71: ---------------------------------------- ok, this makes it even easier :-) AFAICS, the SettingsWriter writes to org.eclipse.jdt.core.prefs. It doesn't generate the complete file, but reads out the already set parameters and overrides the "o.e.j.c.c.compliance", "o.e.j.c.c.source" and "o.e.j.c.c.target" properties. The question now is: Should we delete the file or not? In my projects, org.eclipse.jdt.core.prefs is shared via SVN (e.g. to set project specific code styles) and deleting it is problematic and I don't think necessary. IIUC, the only file within the .settings directory that should get deleted with eclipse:clean is ".settings/.component", which is generated by the EclipseWtpComponentWriter. I could provide a patch if you want. 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]
