Home » Eclipse Projects » Plugin Development Environment (PDE) » WORKSPACE, .metadata, solutions files, project files
| WORKSPACE, .metadata, solutions files, project files [message #2030] |
Tue, 06 May 2008 01:07  |
 Derek Lac
Messages: 19
Registered: July 2009 |
Junior Member |
|
|
Hello,
I am trying to understand who Eclipse works in terms of Workspace,
..metadata, solutions files, and project. I need to know because I am CRM
admin, and I need to check in the files so other developers can
continue work on the project.
I am getting a feeling that all the .metadata files in workspace are
specific to the project. This makes check them in difficult because
there are about 100 files from the project.
Let's say you have library1, library2. Also, helloword uses library1 and
library2. How types of files are produced? Obviously you have to create
a workspace called c:\myownworkspace. There would be some solutions
files to import the projects and sources from library1 and library2 into
the solutions. (I called it solutions borrowed from the term in visual
studio because I don't know what else to call it in Eclipse).
Question: What is the name of this solutions file? Can there be about
4-5 files I need to check in and ignore the rest? Can I put the
workspace to be in some local directory and ask the developers to ignore
that when they check things in?
-Derek Lac
|
|
|
| Re: WORKSPACE, .metadata, solutions files, project files [message #2044 is a reply to message #2030] |
Tue, 06 May 2008 13:31  |
Eclipse User |
|
|
|
Originally posted by: eclipse-news.rizzoweb.com
Derek Lac wrote:
> Hello,
> I am trying to understand who Eclipse works in terms of Workspace,
> .metadata, solutions files, and project. I need to know because I am CRM
> admin, and I need to check in the files so other developers can
> continue work on the project.
> I am getting a feeling that all the .metadata files in workspace are
> specific to the project. This makes check them in difficult because
> there are about 100 files from the project.
>
>
> Let's say you have library1, library2. Also, helloword uses library1 and
> library2. How types of files are produced? Obviously you have to create
> a workspace called c:\myownworkspace. There would be some solutions
> files to import the projects and sources from library1 and library2 into
> the solutions. (I called it solutions borrowed from the term in visual
> studio because I don't know what else to call it in Eclipse).
The most important thing to realize is that the workspace (and its
..metadata directory) are NOT intended to be shared or checked in. A
workspace is highly specific to the machine and environment it is
created in, so trying to share it will only lead to headaches.
The workspace is a logical container for projects, and the project
configurations are what should be shared. For a Java project, that means
at least 2 files, .project and .classpath, along with the project's
contents (source files, etc.). There is also possibly a .settings
directory that can be shared, depending on whether or not you set up
project-specific settings.
Eclipse also has the idea of a Team Project Set, which is a small file
that defines a group of projects and how they are associated with SCM
(usually CVS or SVN). When you have a group of projects (like library1,
library2, and helloworld in your example above) that should be checked
out together, you can select them and then choose File > Export > Team
Project Set. That will produce a file which, when imported into another
workspace, will automatically set up a connection to the SCM repository
and check out the projects.
The Eclipse Help has more details on all of this.
So the bottom line is: don't share workspaces, check in .project and
..classpath files with the projects, and use Project Set files to share a
definition of a group of projects that belong together.
Hope this helps,
Eric
|
|
|
| Re: WORKSPACE, .metadata, solutions files, project files [message #566417 is a reply to message #2030] |
Tue, 06 May 2008 13:31 |
Eric Rizzo
Messages: 3070
Registered: July 2009 |
Senior Member |
|
|
Derek Lac wrote:
> Hello,
> I am trying to understand who Eclipse works in terms of Workspace,
> .metadata, solutions files, and project. I need to know because I am CRM
> admin, and I need to check in the files so other developers can
> continue work on the project.
> I am getting a feeling that all the .metadata files in workspace are
> specific to the project. This makes check them in difficult because
> there are about 100 files from the project.
>
>
> Let's say you have library1, library2. Also, helloword uses library1 and
> library2. How types of files are produced? Obviously you have to create
> a workspace called c:\myownworkspace. There would be some solutions
> files to import the projects and sources from library1 and library2 into
> the solutions. (I called it solutions borrowed from the term in visual
> studio because I don't know what else to call it in Eclipse).
The most important thing to realize is that the workspace (and its
..metadata directory) are NOT intended to be shared or checked in. A
workspace is highly specific to the machine and environment it is
created in, so trying to share it will only lead to headaches.
The workspace is a logical container for projects, and the project
configurations are what should be shared. For a Java project, that means
at least 2 files, .project and .classpath, along with the project's
contents (source files, etc.). There is also possibly a .settings
directory that can be shared, depending on whether or not you set up
project-specific settings.
Eclipse also has the idea of a Team Project Set, which is a small file
that defines a group of projects and how they are associated with SCM
(usually CVS or SVN). When you have a group of projects (like library1,
library2, and helloworld in your example above) that should be checked
out together, you can select them and then choose File > Export > Team
Project Set. That will produce a file which, when imported into another
workspace, will automatically set up a connection to the SCM repository
and check out the projects.
The Eclipse Help has more details on all of this.
So the bottom line is: don't share workspaces, check in .project and
..classpath files with the projects, and use Project Set files to share a
definition of a group of projects that belong together.
Hope this helps,
Eric
|
|
|
Goto Forum:
Current Time: Sat Aug 10 07:38:33 GMT 2024
Powered by FUDForum. Page generated in 0.03883 seconds |
] 
Search
Help
Register
Login
Home
