| Summary: | cleanup .metadata on command or auto | ||
|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Missing name <soloturn> |
| Component: | IDE | Assignee: | Platform-UI-Inbox <Platform-UI-Inbox> |
| Status: | RESOLVED INVALID | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | daniel_megert, remy.suen |
| Version: | 3.7 | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
|
Description
Missing name
Each .metadata child directory is owned by different components. Those components are responsible for its size, either by ensuring that old data gets automatically deleted or by offering options to control the stored size. >* .metadata\.plugins\org.eclipse.jdt.core (more than a year) This keeps the search index of the types and members in your workspace and other information (e.g. external class folders). Are you saying that you know for sure it contains unused data that can be deleted? If so, that would be a bug in JDT Core and should be reported there. >* .metadata\.plugins\org.eclipse.core.resources\.history (nearly a month) The history goes as big as you choose on Workspace > Local History. You can lower the values there if you want. If you think it contains data older than specified by those options then please report a bug against Platform Resources. >* org.maven.ide.eclipse contains "nexus" enourmous Please file a bug report against Maven. I'm closing this as INVALID not because I think there is no bug but because the platform can't do anything generic here. You need to file bugs against the individual components if you think they keep outdated data or if you want an option to control the stored data. |