every projects in eclipse has 4 .files(.settings,.classpath,.cprojects , .projects).
can explain me why these files generated , happens if delete these 4 files. have deleted these files 1 app resulted in changing name of app.
eclipse runtime environment plugins. virtually see in eclipse result of plugins installed on eclipse, rather eclipse itself.
the .project file maintained core eclipse platform, , goal describe project generic, plugin-independent eclipse view. what's project's name? other projects in workspace refer to? builders used in order build project? (remember, concept of "build" doesn't pertain java projects, other types of projects)
the .classpath file maintained eclipse's jdt feature (feature = set of plugins). jdt holds multiple such "meta" files in project (see .settings directory inside project); .classpath file 1 of them. specifically, .classpath file contains information jdt feature needs in order compile project: project's source folders (that is, compile); output folders (where compile to); , classpath entries (such other projects in workspace, arbitrary jar files on file system, , forth).
blindly copying such files 1 machine may risky. example, if arbitrary jar files placed on classpath (that is, jar files located outside workspace , referred-to absolute path naming), .classpath file rendered non-portable , must modified in order portable. there best practices can followed guarantee .classpath file portability.
the .settings folder used various plugins set persistent 'properties' opposed 'prefereneces' specify project specific settings should preserved.
.settings directory want checked svn/cvs/git etc ensure users check project out eclipse use right project specific settings.
in our case use supply minimum compiler version of java want things compiled 5 our servers. use enforce coding standards , auto-formaters makes version diffs easier read.
in specific case selected 'enable project specific settings' under "properties->java compiler" right clicking on project , choosing properties.
