Eclipse Community Forums: ServerTools (WTP) » Understand the Eclipse files in a Dynamic Web Project

Home » Language IDEs » ServerTools (WTP) » Understand the Eclipse files in a Dynamic Web Project

Understand the Eclipse files in a Dynamic Web Project [message #227202]

Mon, 26 January 2009 01:37

Eclipse User

The files residing in .settings in a Dynamic Web Project are:

settings/
|-- org.eclipse.jdt.core.prefs
|-- org.eclipse.jst.common.project.facet.core.prefs
|-- org.eclipse.jst.j2ee.ejb.annotations.xdoclet.prefs
|-- org.eclipse.wst.common.component
|-- org.eclipse.wst.common.project.facet.core.xml
|-- org.eclipse.wst.jsdt.ui.superType.container
|-- org.eclipse.wst.jsdt.ui.superType.name
`-- org.eclipse.wst.validation.prefs

The above file list is pretty much a clean new Dynamic Web Project, except
that I'm using the IvyDE plug in, but I think it only affects the
classpath file.

How do I learn more about these files? I'm wondering if I can get rid of
any of them without loosing something important? Finding this information
at Eclipse.org was not very easy, a link or an explanation would be very
welcome.

I'm trying to learn more about these files as I want to slim down the
Eclipse files as much as possible before I check them into version control.

In case it helps I list the above files and their contents at
http://pastebin.com/f5cb6a072 .

Re: Understand the Eclipse files in a Dynamic Web Project [message #227276 is a reply to message #227202]

Mon, 26 January 2009 14:26

Eclipse User

> How do I learn more about these files?

I am afraid there is no specific documentation detailing these files and
their purposes. Everything starting with '.' in project root (including
the .settings) directory and all of its contents are considered internal
implementation details.

> I'm wondering if I can get rid of any of them without loosing something
> important? ... I'm trying to learn more about these files as I want to slim
> down the Eclipse files as much as possible before I check them into version
> control.

You shouldn't delete any of these files. Everything in .settings directory
and all of the files starting with '.' in project root should be put into
your source control repository if you expect others to be able to import
your projects into Eclipse.

What functionality gets affected if one of these files is missing differs
depending on a file. In some cases, you would loose some settings that
might cause problems that you took care of already to come back, in other
cases, the projects will be completely crippled.

- Konstantin

Previous Topic:	Re: How to let Eclipse deploy 1 (!) *.war file instead of expanded war directory tree?
Next Topic:	Upcoming change to behavior of Java EE module refactoring

Goto Forum:

-=] Back to Top [=-

Current Time: Mon Sep 15 06:40:51 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter